4 ms·
and how is HTTPS protecting us against that? if you took over that IP address you can initiate a valid HTTPS session using the compromised server's identity and
by istvan__ 11y ago
and how is HTTPS protecting us against that? if you took over that IP address you can initiate a valid HTTPS session using the compromised server's identity and communicate with the monitoring service happily reporting fake data over HTTPS. I don't see your point. The question here is btw. is it worth X amount of dollar to protect this service with a secure channel? Sometimes the answer is yes, sometimes it is no.
- zobzu 11y agothe internal server is always made of servers and clients just like the external one. if you compromise one server you have access to the data transiting there, but not the others if you compromise one client you have access to the data this client sends only in particular, very few internal networks enforce L2 security (ie its possible to sniff all data on the same VLAN as you are).