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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
You’ve Been Attacked. Now What?
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
10/28/2015 | 4:35:51 PM
Re: Thanks
Indeed, companies have found their liability favorably reduced/eliminated in situations where they simply addressed cybersecurity enough at board meetings.  There are more benefits to security than mere security.
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
10/28/2015 | 4:33:28 PM
Re: Thanks
And, of course, ideally, for major enterprises and even some SMEs, there was some pre-investigation involvement with law enforcement contacts -- for instance, meet-and-greets and tabletop exercises in preparation for better security postures and more effective involvement should the day come when it is necessary.
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
10/28/2015 | 4:31:47 PM
Re: Thanks
@Ryan: Good point.  We are now at the level where we have everything but a Chief Making Sure There Are Enough Paper Towels in the Men's Room Officer.  "C-level" is losing its meaning and import.
Enrico Fontan
Enrico Fontan,
 User Rank: Strategist
10/27/2015 | 7:39:30 PM
Re: Thanks
@ryanvela/@Ryan/@Joe I agree with the C-level security concept. During critical events a CISO need to be able to interact at C-level to be fast and operate in a transparent way.

If the CISO reports to the CIO I hardly think that such a step could be possible:

"Involved the local FBI office at the start of the investigation"
ryanvela
ryanvela,
 User Rank: Apprentice
10/27/2015 | 6:59:58 PM
Re: Thanks
@Ryan and @Joe, you both have good points.  I have worked cases with organizations that have and do not have formal CISO positions.  One organization had the CISO reporting to the CIO, another had the CISO reporting to the CFO, and I am aware of an organization where the CIO reports to the CISO, but I have not worked on a breach for that type of organization.  Nevertheless, all of the organizations have a person that carries the function of the CISO, regardless of the person's title, whether they report to the board, or what staff they have under them.  But two changes (new or enhanced) I have found that organizations that have gone through breaches initiate:  1. Cybersecurity maintains top-down advocacy; and by top, obviously the C-suite; and  2. Cybersecurity has a voice at regular board meetings; not just once a year at the "cyber review" meeting.
RyanSepe
RyanSepe,
 User Rank: Ninja
10/27/2015 | 8:41:22 AM
Re: Thanks
@Joe. Very true. I think it comes down to how your corporate environment is structured. Do most of the C level employees report to the board? If yes, then the CISO should as well.

Or is a C level position given to so many people that everyone is a C level for something. In a case like this it becomes unmanageable. I know the latter case sounds not applicable, but I just wanted to poke at the Chief level being put in front of many job titles with high specificity when it probably shouldn't.
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
10/26/2015 | 11:06:45 PM
Re: Thanks
@Ryan: There is a lot of debate regarding to whom the CISO should report.  The CIO is often the typical and obvious choice, but the CIO and the CISO often have conflicting goals -- budgetary, political, and more.  Many think the CISO should report to the CFO or even the CEO.  Others think the CISO should report directly to the board.
RyanSepe
RyanSepe,
 User Rank: Ninja
10/26/2015 | 7:48:34 AM
Re: Thanks
This is why security needs to have an equal seat at the table. A CISO should be able to bring pivotal points to light and delineate why its imperative to get things moving as soon as possible. Ideally...


Unfortunately, many times this is not the case.
ryanvela
ryanvela,
 User Rank: Apprentice
10/25/2015 | 12:45:04 AM
Re: Thanks
Excellent observation.  I can attest to receiving Monday morning calls from CISOs after they've known of an incident since the previous week.  Not only that, I see well meaning security groups struggle with containing a situation they found earlier in the week only to find themselves tired, frustrated, and annoyed Friday afternoon.  Friday afternoons and Monday mornings are when I get most of my calls for assistance.
Joe Stanganelli
Joe Stanganelli,
 User Rank: Ninja
10/24/2015 | 2:59:47 PM
Thanks
An important article for executives to read.  Alas, many CEOs and CIOs take the attitude, when faced on Friday afternoon with news of an attack or other intrusion or compromise, of "We'll deal with it first thing Monday."


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