Endpoint
7/25/2013
02:49 PM
Doug Landoll
Doug Landoll
Commentary
Connect Directly
RSS
E-Mail
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
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6306
Published: 2014-08-22
Unspecified vulnerability on IBM Power 7 Systems 740 before 740.70 01Ax740_121, 760 before 760.40 Ax760_078, and 770 before 770.30 01Ax770_062 allows local users to gain Service Processor privileges via unknown vectors.

CVE-2014-0232
Published: 2014-08-22
Multiple cross-site scripting (XSS) vulnerabilities in framework/common/webcommon/includes/messages.ftl in Apache OFBiz 11.04.01 before 11.04.05 and 12.04.01 before 12.04.04 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, which are not properly handled in a (1)...

CVE-2014-3525
Published: 2014-08-22
Unspecified vulnerability in Apache Traffic Server 4.2.1.1 and 5.x before 5.0.1 has unknown impact and attack vectors, possibly related to health checks.

CVE-2014-3563
Published: 2014-08-22
Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1) seed.py, (2) salt-ssh, or (3) salt-cloud.

CVE-2014-3587
Published: 2014-08-22
Integer overflow in the cdf_read_property_info function in cdf.c in file through 5.19, as used in the Fileinfo component in PHP before 5.4.32 and 5.5.x before 5.5.16, allows remote attackers to cause a denial of service (application crash) via a crafted CDF file. NOTE: this vulnerability exists bec...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.