Endpoint
7/25/2013
02:49 PM
Doug Landoll
Doug Landoll
Commentary
50%
50%

SMB Insider Threat: Setting Behavior Boundaries

Two major policies should be in place to guide and restrict user behavior

Small and midsized business (SMB) employees who have made it past any employment screening in place may still pose a threat to the SMB systems and assets. SMB insiders can reveal confidential information, subvert security controls, and introduce malicious code into the network, but these misbehaving employees are not always malicious, and their behavior is not always illegal. Therefore, it is important to implement appropriate security policies to guide the well-meaning employee away from dangerous behavior and to formally document unacceptable behaviors in which sanctions may be applied for those intentionally damaging the company.

This is the second part of a blog series on the SMB insider threat and what to do about it. The first part of the series covered employment screening issues for SMBs; this part covers policy controls.

Two major policies should be in place to guide and restrict user behavior: data classification and acceptable use. Data classification policies protect sensitive data. Acceptable use policies ensure proper use of company systems.

Data Classification Policies: The key to an effective data classification policy is to define confidential data and associate the controls required for its protection. The best approach is to list categories of sensitive data that require different levels of protection. Keep the number of categories low -- two or three. Examples of data classification categories include Public (i.e., releasable), Sensitive (e.g., proprietary), and Highly Sensitive (e.g., protected health information, cardholder data). Now associated required controls for each category of data. Data-handling controls should cover identification and labeling, handling, transmission, processing, and media protection.

Acceptable Use Policies: The key to an effective acceptable use policy is to ensure it is clear and accessible by employees. My test for clarity is to simply ask employees a question regarding the acceptable use of the network and premises, such as, "Are we allowed to bring camera phones into the sensitive areas (e.g., data center, patient room)?" If they are unable to use the acceptable use policy to find the answer, then the policy is unorganized and unclear. Organizing the contents of the acceptable use policy ensures the clarity of the policies to users. For example, all acceptable use policy statements should fall into one of the following four categories: Prohibited Items, Prohibited Behaviors, Expected Behaviors, and Notifications. Our question above can be answered in the "Prohibited Items" section.

General Security Policy Advice

It is tempting to search the Internet for policy examples and simply substitute the company name to make it your own. Please avoid this approach. Each SMB differs from others in its culture, sensitive data, existing controls, and security approach. By all means use found policies as templates or examples, but carefully consider each policy statement prior to adopting it as your standard.

Doug Landoll is the CEO of Assero Security, a firm specializing in SMB Security. You can follow him on Twitter as @douglandoll Doug Landoll is an expert in information security for the SMB market with over 20 years experience securing businesses and government agencies. He has written several information security books and dozens of articles for national publications. He has founded and ran four ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
DilM269
50%
50%
DilM269,
User Rank: Apprentice
7/30/2013 | 5:52:49 AM
re: SMB Insider Threat: Setting Behavior Boundaries
i totally agree with you sir.

http://resultplanet.org
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading, January 2015
To find and fix exploits aimed directly at your business, stop waiting for alerts and become a proactive hunter.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-7402
Published: 2014-12-17
Multiple unspecified vulnerabilities in request.c in c-icap 0.2.x allow remote attackers to cause a denial of service (crash) via a crafted ICAP request.

CVE-2014-5437
Published: 2014-12-17
Multiple cross-site request forgery (CSRF) vulnerabilities in ARRIS Touchstone TG862G/CT Telephony Gateway with firmware 7.6.59S.CT and earlier allow remote attackers to hijack the authentication of administrators for requests that (1) enable remote management via a request to remote_management.php,...

CVE-2014-5438
Published: 2014-12-17
Cross-site scripting (XSS) vulnerability in ARRIS Touchstone TG862G/CT Telephony Gateway with firmware 7.6.59S.CT and earlier allows remote authenticated users to inject arbitrary web script or HTML via the computer_name parameter to connected_devices_computers_edit.php.

CVE-2014-7170
Published: 2014-12-17
Race condition in Puppet Server 0.2.0 allows local users to obtain sensitive information by accessing it in between package installation or upgrade and the start of the service.

CVE-2014-7285
Published: 2014-12-17
The management console on the Symantec Web Gateway (SWG) appliance before 5.2.2 allows remote authenticated users to execute arbitrary OS commands by injecting command strings into unspecified PHP scripts.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.