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.

Attacks/Breaches

1/22/2015
03:00 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

NSA Report: How To Defend Against Destructive Malware

In the wake of the Sony breach, spy agency's Information Assurance Directorate (IAD) arm provides best practices to mitigate damage of data annihilation attacks.

Prevent, detect, and contain: Those are the key overarching strategies for combating data-destroying malware attacks, according to a new report issued this month by the National Security Agency.

The NSA's Information Assurance Directorate (IAD) outlined key best practices for defending against such attacks-- à la Sony or Saudi Aramco -- that require organizations being proactive rather than reactive to a cyberattack.

"Once a malicious actor achieves privileged control of an organization's network, the actor has the ability to steal or destroy all of the data that is on the network," the NSA says in its new "Defensive Best Practices for Destructive Malware" report. 

The report comes in the wake of the massive and destructive attack on Sony, and includes some already well-known best security practices. 

Some tools can mitigate some of the damage, the report says, but preventing the attacker from getting control over the network is a more effective defense. "The earlier that network defenders can detect and contain an intrusion, the less damage the intruder can possible cause," the report says. Planning for the worst-case scenario is also key, according to the NSA.

NSA's recommendations recap some strategies the NSA previously had published in its "Information Assurance Mitigation Strategies" report. Among the best practices in the latest report for preventing, detecting, and containing attacks are:

  • Segregate network systems and functions so that if an attacker hacks in one area, he can't necessarily reach others
  • Reduce and protect administrator privileges to minimize the damage if a bad guy obtains them
  • Employ application whitelisting to prevent malicious code from executing
  • Limit workstation-to-workstation communication to reduce the attack surface
  • Run perimeter firewalls, application-layer firewalls, forward proxies, and sandboxing or other dynamic traffic and code analyses
  • Use and monitor host and network logging
  • Implement pass-the-hash mitigations
  • Run Microsoft's EMET or other anti-exploit tools
  • Employ antivirus reputation services to augment traditional signature-based AV
  • Run host intrusion prevention systems
  • Regularly update and patch software

On the incident response side, NSA recommends an incident response plan and regular testing of the plan. "Preparing through offline backups and exercised incident response and recovery plans can make the organization more resilient, enabling quick reconstitution and the resumption of normal business functions as soon as possible," the report says.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
andregironda
50%
50%
andregironda,
User Rank: Strategist
1/23/2015 | 1:49:16 PM
Quick!
Pull the plug!!!
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
1/23/2015 | 3:45:23 PM
Re: Quick!
As long as you don't pull it after an attack--then there's no forensics trail. =)
macker490
50%
50%
macker490,
User Rank: Ninja
1/24/2015 | 10:17:09 AM
Start at the Beginning
1. use a secure O/S.

2. look into using Named Spaces

remember that in implementing RACF on an MVS system access had to be granted on an item by item basis.  this is fundamental to security.    it gives you control over who has access to do what using the various tools available.   Your access list is an auditable item.    make sure your auditor knows how you are controlling access.

restricting access to files based on user ID is inadequate for any user who is running programs of an un-known nature.   remember: modern documents -- web pages, e/mail, and such must be treated as executable files where it is possible that the documents contains or links to something that is executable.

2014 has been headlined as "The Year of the Hack".    unless we start doing things differently 2015 will be more of the same.   Change will be painful as it so often is.   But at some point it becomes the only acceptable option.
Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: What Virtual Reality phishing attacks will look like in 2030.
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
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-21652
PUBLISHED: 2021-05-11
A cross-site request forgery (CSRF) vulnerability in Jenkins Xray - Test Management for Jira Plugin 2.4.0 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
CVE-2021-21653
PUBLISHED: 2021-05-11
Jenkins Xray - Test Management for Jira Plugin 2.4.0 and earlier does not perform a permission check in an HTTP endpoint, allowing with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
CVE-2021-21654
PUBLISHED: 2021-05-11
Jenkins P4 Plugin 1.11.4 and earlier does not perform permission checks in multiple HTTP endpoints, allowing attackers with Overall/Read permission to connect to an attacker-specified Perforce server using attacker-specified username and password.
CVE-2021-21655
PUBLISHED: 2021-05-11
A cross-site request forgery (CSRF) vulnerability in Jenkins P4 Plugin 1.11.4 and earlier allows attackers to connect to an attacker-specified Perforce server using attacker-specified username and password.
CVE-2021-21656
PUBLISHED: 2021-05-11
Jenkins Xcode integration Plugin 2.0.14 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.