Poor Network Control Policies
Security Manual Template and Compliance Tools
src="https://www.e-janco.com/images/Key-security-small.jpg"
align=right>Using Plain FTP
Its way too cheap and easy to download a free FTP tool off the
Internet, or even use a command-line for those savvy computer users. Plain
FTP is sent in the clear across the network, prime for a
man-in-the-middle attack or to assist bad actors with a data breach.
Organizations that use plain FTP open themselves up to attack, giving
intruders free reign in their network.
Not Keeping Systems and Software Up to Date
Microsoft and other software organizations release frequent updates. They
dont release these updates out of the goodness of their hearts; they do
it because security holes were found in their code, in Java, or in
OpenSSL, and they need to patch the software. Not keeping systems and
software up to date is just shooting yourself in the foot. Its worth the
temporary annoyance to make your data a little more secure. This includes
keeping certificates current.
Not Knowing Whats Happening on Your Network
If you are monitoring whats coming into and going out of your network,
as well as who is connecting and when, thats a big step in controlling
your network. Also, if you have multiple systems to manage, its much
easier to get a clear picture of what is going on if all of the data is
monitored in one location. You should include in your security policy a
requirement for periodic reports, email alerts, and other real-time
indicators of activity on the network.
alt=""
src="https://www.e-janco.com/images/Buttons/Order_Security_Manual.png">
alt="Download Selected Pages"
src="https://www.e-janco.com/images/Buttons/Download_Pages.png">