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.

Partner Perspectives  Connecting marketers to our tech communities.
SPONSORED BY
1/11/2017
03:00 PM
Malwarebytes Labs
Malwarebytes Labs
Partner Perspectives
50%
50%

Operational Security Best Practices For Social Media

Building a firm, clear policy on disclosures online can provide a flexible, adaptive response that will protect proprietary data from winding up in a public leak.

In recent years, we’ve seen the pace of database breaches and the subsequent distribution of Personally Identifiable Information (PII) accelerate to a breakneck pace, causing significant financial and personal damage to the individuals impacted.  But what often goes unconsidered is the organizational damage that the loss of even a single email address can cause. 

One carefully considered stolen pair of credentials can offer a jumping off point for a phishing campaign that appears to come from a trusted source, an intelligence source that affords an attacker targeting data for subsequent action, or a pivot point to access other accounts that may use the same password. In fact, attackers will commonly comb through leaked databases for high value targets and resell secondary lists to those looking to use the accounts before a password reset.  A common defense against these sort of scenarios is practicing good organizational social media operational security – OPSEC - principally by keeping company data off LinkedIn, Facebook, Reddit, and the like. 

OPSEC on social media demands good communication between first-line managers, legal policy, and your Security Operations Center (SOC).  Legally, you can’t forbid your employees from using LinkedIn, but you can bar them from disclosing company assets publically, such as an organizational email.  First-line managers are responsible for implementing legal policies, but more importantly – these managers can communicate back to the OpSec team when business needs are forcing employees to circumvent security policies. 

Much more common than the malicious insider threat is the employee who can’t access data they need on the road, and decides to forward company email to a webmail service.  Another dangerous scenario is the employee who is required to disclose their company email to third parties, but doesn’t have a separate account for sensitive data. 

SOC: Your OPSEC Of Last Resort
There are generally simple, easy fixes for these issues that tend not to be implemented due to poor communication with first-line managers.  And there will always be individuals with exceptionally poor judgment, for example, those who would register for ashleymadison.com with a company email.  Bottom line, making sure security policies are aligned with business needs is a low cost measure that decision makers should be doing as a matter of course.

The SOC affords your organization with OPSEC of last resort. If a SOC tech sees company information disclosed in a public space, something has already gone wrong.  That said, a simple crawler set to look for a defined keyword or domain list on sites like Reddit or Facebook can find leaked PII fast, increasing the odds that a takedown will be more effective. 

A Tier II SOC tech can triage a leak after the fact by pinpointing the precise point of egress.  Asking for passive monitoring of PII can afford an additional layer of security for situations when policy is not sufficient.  Brand Protection services will also do this as part of a vendor relationship, although typically at significant cost. 

As with most cybersecurity issues, protecting company information on social media boils down to issues of communication.  Building firm, clear policy on disclosures online, as well as providing channels for feedback to filter upwards, can provide a flexible, adaptive response that will protect proprietary data from winding up in a public leak.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-28487
PUBLISHED: 2021-01-22
This affects the package vis-timeline before 7.4.4. An attacker with the ability to control the items of a Timeline element can inject additional script code into the generated application.
CVE-2021-21260
PUBLISHED: 2021-01-22
Online Invoicing System (OIS) is open source software which is a lean invoicing system for small businesses, consultants and freelancers created using AppGini. In OIS version 4.0 there is a stored XSS which can enables an attacker takeover of the admin account through a payload that extracts a csrf ...
CVE-2021-21270
PUBLISHED: 2021-01-22
OctopusDSC is a PowerShell module with DSC resources that can be used to install and configure an Octopus Deploy Server and Tentacle agent. In OctopusDSC version 4.0.977 and earlier a customer API key used to connect to Octopus Server is exposed via logging in plaintext. This vulnerability is patc...
CVE-2020-4766
PUBLISHED: 2021-01-22
IBM MQ Internet Pass-Thru 2.1 and 9.2 could allow a remote user to cause a denial of service by sending malformed MQ data requests which would consume all available resources. IBM X-Force ID: 188093.
CVE-2021-21259
PUBLISHED: 2021-01-22
HedgeDoc is open source software which lets you create real-time collaborative markdown notes. In HedgeDoc before version 1.7.2, an attacker can inject arbitrary JavaScript into a HedgeDoc note, which is executed when the note is viewed in slide mode. Depending on the configuration of the instance...