Good Day!
My name is Dave Zmeyr and I?m in the architecture group specializing in security for the company that I work for.
Our approach to security has been to:
Identify potential points of egress
Implement proven solutions
?Policify?best practices
It?s important to note that security is a multi-pronged tool that needs to be implemented.
Policies / Rules
Most security breaches are due, frankly, to simple failures to follow common sense rules ? for example, implementing MS SQL Server and not giving the default ID a new password.
Security also can easily become a struggle between the person trying to implement and improve security, the user community and developer community.
Common rules when dealing with thesetwo communities is to obtain senior business level buy-in on basic necessary security rules and then allow the business units to propagate the rules ?you can monitor and inform, but don?t try and be ?judge, jury and executioner? ? otherwise users will perceive you as just that and do their utmost to work around you.
There are many forums that provide common sense rules ? if you need some samples you can e-mail me directly and I?ll be happy to provide some.
Identify Points of Egress
Most security breaches occur from internal sources ? but it?s the external ones that get the presses. An example is all of the credit card fraud that we hear about constantly on the web.
Consider your enterprise the same way you consider your house;install strong doors with locks (firewalls), don?t leave vital papers lying in the living room (segregate your network ? build a DMZ), put in a good alarm system (intrusion detection systems), and don?t forget to put out any fires that you find! (remediate, remediate! Apply patches and fix bad settings).
Implement proven solutions
You don?t need to be an expert with Brinks to understand that an alarm system is good ? at
