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
Why Digital Forensics In Incident Response Matters More Now
Newest First  |  Oldest First  |  Threaded View
JasonSachowski
JasonSachowski,
User Rank: Author
12/29/2014 | 9:02:03 AM
Re: Why Digital Forensics In Incident Response Matter More Now
While I agree that proven forensic tools are essential, we cannot rely on technology to catch the bad guy.  Let's not forget that in order to make these forensic tools work, knowledgeable people and established processes are equally important.
Broadway0474
Broadway0474,
User Rank: Apprentice
12/28/2014 | 11:54:46 PM
Re: Knowledge base for attacks
DrT, that is a great point about building a "knowledge base" of past attacks. It's a lesson perhaps transferable from other catastrophe types, like say hurricanes. Experts there study past hurricanes, not that one is replicable --- but more to learn how wind speeds and wave heights affect businesses, communities, etc. in the hopes of applying relatable lessons when the next hurricane comes. Agree it's similar?
Dr.T
Dr.T,
User Rank: Ninja
12/26/2014 | 9:35:32 AM
Re: Being Pro-active with Forensics
I agree on the IP address also. IP address can easily be spoofed, neither source nor destination IPs are reliable. Not even MAC address can really be used to identify the source of a message.
Dr.T
Dr.T,
User Rank: Ninja
12/26/2014 | 9:33:53 AM
Re: Being Pro-active with Forensics
Agree, being proactive and doing the require work and analyzing the treats. It needs to be taken to next level and removing vulnerabilities in the environment
Dr.T
Dr.T,
User Rank: Ninja
12/26/2014 | 9:21:52 AM
Knowledge base for attacks
 

I agree there has to be a knowledge base built for the attacks in the enterprise. This would not only help to understand and prevent from similar types of attacks but also it would give us an idea of the trend around where are being exploited and what our vulnerabilities are. The enterprise can not really continue to fight with attacks that would be very expensive in the long run, we need to understand our vulnerabilities and close them before they are being exploited.
PZav
PZav,
User Rank: Author
12/24/2014 | 1:11:55 PM
Being Pro-active with Forensics
The more I learn about the forensics work we do at RiskIQ, the more I see the value. In our case, our forensics team uses data collected from our detection technology, which scans large sections of the publich web. Our forensics teams analyze threats as they appear online. The benefit being that a potentially innocous looking infection may be tied to a more expansive and sophisticated attack infrastructure.

The reality is that many prominent threat actors share resources and just because one attack may appear to have originated from IPs tied to prior attacks, does not mean that infrastructure is owned by the same group. It could be infrastructure rented out for multiple uses. It helps us understand what our customers might be up against. 


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Everything You Need to Know About DNS Attacks
It's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask. Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted. Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-33196
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences. Cross site scripting (XSS) can be triggered by review volumes. This issue has been fixed in version 4.4.7.
CVE-2023-33185
PUBLISHED: 2023-05-26
Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests ar...
CVE-2023-33187
PUBLISHED: 2023-05-26
Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type="text"` via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates `ty...
CVE-2023-33194
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences on the web.The platform does not filter input and encode output in Quick Post validation error message, which can deliver an XSS payload. Old CVE fixed the XSS in label HTML but didn’t fix it when clicking save. This issue was...
CVE-2023-2879
PUBLISHED: 2023-05-26
GDSDB infinite loop in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via packet injection or crafted capture file