New answers tagged

0

There are some great answers on architecture and correctly designing a network already, so I won't address those. What I haven't seen mentioned is watching for data exfiltration methods. If someone is inside your network, ostensibly they are looking for additional hosts they can compromise and data that might be useful to them. (Credit cards, ...


0

First and foremost, you would never allow guests to access your network. A separate network should be created for them. But let's go with it. So you have a flat network of systems (doesn't matter if they're servers, desktop, etc., everything is flat.) Do you have a documented network? Meaning, do you know what systems are supposed to interconnect with what? ...


0

I just did some research on this as I am in the same seat as you; I've set up a VPN but wanted to make sure that I'm not forwarding the world. Enabling forwarding in the kernel, doesn't mean that everything will pass through iptables firewall. However, if the firewall allows all forwarding, you might be in big trouble. Luckily iptables seem to DROP ...


0

Private keys should exist only in one place. If you distribute the private key to "authorized users", then the "authorized users" have all access of the original, and cannot be revoked. The correct method would be: All devices share their public key, never their private key. The public key is approved by the account holder. Any changes logged should ...



Top 50 recent answers are included