Part II – Security Policy, SMB - Security Is At The Forefront

For a lot of SMB’s a good security policy is the basis for a strong network defense.  However for those companies who have not designed and implemented a security policy within their organizations, security issues are lying in wait.

A security policy is the backbone and foundation for information security.  However in this day and age some SMB’s have ignored or not kept up with current security concerns and their policy or lack of policy may allow for a severe security breach.  This may in fact prove fatal for a SMB.

In Part II of my series for SMB, I am going to look at what makes a good security policy. 

1.  Executive Management Buy In

All security policies should begin with an executive management summary that includes the purpose, direction and approval of the policy.  This informs IT as well as employees that security is supported in all aspects of the business.  Security needs to be addressed from a top down approach when it pertains to support.  By supporting security initiatives from this approach employees know that security is not only implemented but supported at all levels.

2.  Policies

A security policy is actually a collection of different types policies put together to create one policy.  The other types of policies are created from different areas that need to be secured, such as identification, authentication, authorization and auditing.   Other types of policies would include a user access policy, password policy, vpn policy, remote access policy, wireless policy and acceptable use policy.  Each one of these policies would address a certain set of guidelines and procedures when implementing these technologies.

3)  Standards


Each policy will have standards of how the technology can be implemented.  Standards are important because they allow us to measure by a metric.  For example, if the password policy has a minimum length of 8 characters, then when we set passwords we have a value to measure if we have met the standard.

4)  Guidelines

As mentioned earlier, each policy may also have a set of guidelines.  Guidelines are helpful because they allow us to implement technology with variables that may differ from one area to another area.  Guidelines provide a range of values because if we set a standard it may not be appropriate for that technology.  An example of a guideline would be the types of hardware purchased for laptops.  No one laptop may fit all the needs so guidelines are put in place to ensure secure hardware is purchased.

5)      Procedures

These are the details that go along with every policy that explains the how, who, what and when of how the technology is implemented.  An example of a set of procedures would be how a Cisco wireless thin client would be installed and managed.

6)      Acceptable Use Policy

This is part of the security policy that informs everyone on how company assets and resources are to be used inside and outside of the company.  The acceptable use policy has guidelines, procedures and standards from how you can use a company laptop to where you can go on the internet.  It is important that companies ensure this is updated and employees are made aware of changes.

If you would like to get some more information of creating a security policy and download some templates for the creation of different types of policies try SANS: Information Security Policy Templates

Next month in part 3, I will be discussing how SMB’s can implement and improve security awareness. 

Thank you and if you have any questions during the series please feel free to email me at wpruett@centriq.com

Tom Pruett

Network Security Engineer/Senior Technical Instructor

CCSI, CCNA, MCSE (NT, 2000, 2003), MCITP SQL 2005, MCDBA SQL 7 2000, 2005, MCP+1, MCT, CTT+, CISSP, CWNA, CEI, CEH, CHFI, A+, Network+, Security+

Part I - Threats and Vulnerabilities, SMB - Security Is At The Forefront

SMB's share a lot of similarities with large enterprises when it comes to IT Security.  Those similarities include confidentiality of data, preventing unauthorized access and ensuring availability of data.  However, enterprises have the resources such as security personnel to ensure these objectives are achieved.  SMB's have the same threats and vulnerabilities except they may or may not have the the personnel or knowledge that these threats and vulnerabilities may even exist or that they may even be effected by them. 


In Part I of of my "SMB - Security Is At The Forefront" series I am going to explore the unique challenges presented by threats and vulnerabilities for SMB's.


I. Security Policies  - The Key

Whenever I do a security audit for a SMB, the first thing I find is the lack of a specific security policy.  I either find no policy or only a statement in the employee handbook about the AUP (Acceptable User Policy).  This is not enough in this day and age to ensure a secure environment.  First, the owner or owners need to understand that security is important and that their acceptance and support of a security policy is first and foremost.  A written policy explaining the policies, baselines, standards, procedures and who is responsible for security should be created so everyone understands what is to be expected with regards to security.


II. Patching Control

Most SMB's do not have a managed patching system.  By this I mean a centralized method of controlling when and what patches are applied to OS's and applications.  Most SMB's rely on Windows Update to individually update the OS, however it is up to the individual to ensure the updates are applied.  This can mean a workstation might not be updated and have a serious vulnerability.  A major component to a secure system is ensuring that all systems are up to date with the latest patches.  This includes a process that ensures that patches and updates are tested and rolled in a timely fashion.  This can be done easily and effectively by WSUS (Windows Server Update Service).  Also, ensuring a set of procedures to audit to ensure all systems are up to date is very important.

Weak Passwords

This is one of the biggest vulnerabilities for a SMB.  A lot of SMB's have weak password policies or none at all.  Employees are allowed to create passwords on their own for their workstations without any guidelines nor are they made to change them.  Also, in some cases there is no password on the system at all.   A strong password policy is crucial to securing a system.  All employees should be required to have passwords that are at least 8 characters, have a number and a character and should be changed at least every 45 days.

Default Accounts

The use of default accounts is also sometimes an issue.  By this I mean workstations have just a default account on them such as administrator or guest with no password.  This allows anyone to use the system with minimal or no controls creating a vulnerability whereas a hacker or employee could exploit the machine.

Physical Controls

Since most SMB's only have a few offices, there may not be a great need for locks and door security since this is usually done.  However security to the IT closet or where the servers are located needs to be addressed.  Normally having only a few devices does not negate the fact that all servers, routers, switches and firewalls need to be in a secure place and have limited access.


Wireless - Rouge Access Points, Weak Wireless Security

Sometimes SMB's will employ wireless solutions just as they would as if they were installing one at home.  This can be a serious concern because business wireless should not be treated like home wireless.  Business wireless should be concerned with getting connectivity with secure protocols and most importantly controlling access to the wired network.  Basic installation and lack of controls on the use of the wireless usually lead to a security breach.

Lack of Security Awareness

Owner and employees need to be aware of secure practices when doing their job.  All employees should understand the impact on the company if they are working on a computer regardless if it is connected to a network.  Having a good understanding of secure practices will help protect the company from most security breaches.

Next month in part 2, I will be discussing most specifics on how to create a SMB security policy.

Thank you and if you have any questions during the series please feel free to email me at wpruett@centriq.com


Tom Pruett

Network Security Engineer/Senior Technical Instructor
CCSI, CCNA, MCSE (NT, 2000, 2003), MCITP SQL 2005, MCDBA SQL 7 & 2000, MCP+1, MCT, CTT+, CISSP, CWNA, CEI, CEH, CHFI, A+, Network+, Security+