Comments
NotPetya: How to Prep and Respond if You're Hit
Newest First  |  Oldest First  |  Threaded View
RobEnns
50%
50%
RobEnns,
User Rank: Author
7/13/2017 | 2:56:59 PM
Re: What about replicated COOP scenarios
Very good question, interested in the same.
matt.trevors
50%
50%
matt.trevors,
User Rank: Apprentice
7/12/2017 | 12:13:55 PM
We need to stop confusing end users
We in the security community have a very difficult time conveying the importance of various strategies and tactics to end users when it comes to securing their infrastructure.  I believe it in part is because we aren't promoting a unified message. Instead, we tell them what we "think" are the right things to do.  Instead, why don't you preach about the adoption of existing well-documented strategies and tactics?  For instance, you could have pointed end users to the Center for Internet Security Critical Security Controls (formerly SANS 20) which would include standing up an incident response plan, patching boxes, and backing up high-value assets.  Also, you could have pointed people to NIST 800-61 Computer Security Incident Handling Guide which would give them a good idea of how to stand up incident response capabilities for their organization (planning, detection & analysis, containment, eradication, recovery, and post-incident activities).  Finally, you are dancing around the NIST Cybersecurity Framework which includes functions, categories, and subcategories that describe how to identify, protect, detect, respond, and recover.  

As a community, we need to get better at getting our message across or things are never going to get better.  To do that, we all need to get on the same page and back published standards.  If you don't agree with the standards, most encourage community feedback.
randyfromsd
50%
50%
randyfromsd,
User Rank: Apprentice
7/11/2017 | 4:23:26 PM
Re: What about replicated COOP scenarios
Isolate the backup target from the network - make shares hidden so they aren't easily accessible - restrict user accounts - implement local\offsite backup.
jenshadus
50%
50%
jenshadus,
User Rank: Strategist
7/10/2017 | 8:35:09 AM
What about replicated COOP scenarios
Just curious of how a malware attack would affect an active-active DR scenario.  If the malware can infect a primary target, I would think it would affect the backup environment.  And what would this do to the backup recovery plans?  Sounds like the best bet is to still use tape backup.


White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
The Fundamental Flaw in Security Awareness Programs
Ira Winkler, CISSP, President, Secure Mentem,  7/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14492
PUBLISHED: 2018-07-21
Tenda AC7 through V15.03.06.44_CN, AC9 through V15.03.05.19(6318)_CN, and AC10 through V15.03.06.23_CN devices have a Stack-based Buffer Overflow via a long limitSpeed or limitSpeedup parameter to an unspecified /goform URI.
CVE-2018-3770
PUBLISHED: 2018-07-20
A path traversal exists in markdown-pdf version <9.0.0 that allows a user to insert a malicious html code that can result in reading the local files.
CVE-2018-3771
PUBLISHED: 2018-07-20
An XSS in statics-server <= 0.0.9 can be used via injected iframe in the filename when statics-server displays directory index in the browser.
CVE-2018-5065
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have a Use-after-free vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.
CVE-2018-5066
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have an Out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.