Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

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
COVID-19: Latest Security News & Commentary
Dark Reading Staff 11/19/2020
New Proposed DNS Security Features Released
Kelly Jackson Higgins, Executive Editor at Dark Reading,  11/19/2020
How to Identify Cobalt Strike on Your Network
Zohar Buber, Security Analyst,  11/18/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25159
PUBLISHED: 2020-11-24
499ES EtherNet/IP (ENIP) Adaptor Source Code is vulnerable to a stack-based buffer overflow, which may allow an attacker to send a specially crafted packet that may result in a denial-of-service condition or code execution.
CVE-2020-25654
PUBLISHED: 2020-11-24
An ACL bypass flaw was found in pacemaker before 1.1.24-rc1 and 2.0.5-rc2. An attacker having a local account on the cluster and in the haclient group could use IPC communication with various daemons directly to perform certain tasks that they would be prevented by ACLs from doing if they went throu...
CVE-2020-28329
PUBLISHED: 2020-11-24
Barco wePresent WiPG-1600W firmware includes a hardcoded API account and password that is discoverable by inspecting the firmware image. A malicious actor could use this password to access authenticated, administrative functions in the API. Affected Version(s): 2.5.1.8, 2.5.0.25, 2.5.0.24, 2.4.1.19.
CVE-2020-29053
PUBLISHED: 2020-11-24
HRSALE 2.0.0 allows XSS via the admin/project/projects_calendar set_date parameter.
CVE-2020-25640
PUBLISHED: 2020-11-24
A flaw was discovered in WildFly before 21.0.0.Final where, Resource adapter logs plain text JMS password at warning level on connection error, inserting sensitive information in the log file.