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.

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.


News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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-2021-29450
PUBLISHED: 2021-04-15
Wordpress is an open source CMS. One of the blocks in the WordPress editor can be exploited in a way that exposes password-protected posts and pages. This requires at least contributor privileges. This has been patched in WordPress 5.7.1, along with the older affected versions via minor releases. It...
CVE-2021-21405
PUBLISHED: 2021-04-15
Lotus is an Implementation of the Filecoin protocol written in Go. BLS signature validation in lotus uses blst library method VerifyCompressed. This method accepts signatures in 2 forms: "serialized", and "compressed", meaning that BLS signatures can be provided as either of 2 un...
CVE-2021-29430
PUBLISHED: 2021-04-15
Sydent is a reference Matrix identity server. Sydent does not limit the size of requests it receives from HTTP clients. A malicious user could send an HTTP request with a very large body, leading to memory exhaustion and denial of service. Sydent also does not limit response size for requests it mak...
CVE-2021-29431
PUBLISHED: 2021-04-15
Sydent is a reference Matrix identity server. Sydent can be induced to send HTTP GET requests to internal systems, due to lack of parameter validation or IP address blacklisting. It is not possible to exfiltrate data or control request headers, but it might be possible to use the attack to perform a...
CVE-2021-29432
PUBLISHED: 2021-04-15
Sydent is a reference matrix identity server. A malicious user could abuse Sydent to send out arbitrary emails from the Sydent email address. This could be used to construct plausible phishing emails, for example. This issue has been fixed in 4469d1d.