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
Vulnerability Management: The Most Important Security Issue the CISO Doesn't Own
Newest First  |  Oldest First  |  Threaded View
Dimitri Chichlo
Dimitri Chichlo,
 User Rank: Apprentice
1/19/2018 | 5:09:55 AM
Automation: yes, but...
I do not fully agree with automatic patching. You never know the side effects of applying a patch. My approach is that you should first deploy on a few workstations or on a test server for critical applications, then test, then deploy full-scale. Otherwise the impact on availability of systems can be dramatic.

One of the issues faced by infra is that some patches are often marked as missing, although a newer one is superseding. This creates headaches.

And risk-based approach is also key. Do you need to patch everything? 

Some systems do not need to be patched every month, like MS servers. You can check for new patches every quarter or every six months. Is there a need for automation then? 
MichaelM17101
MichaelM17101,
 User Rank: Strategist
1/9/2018 | 8:57:24 AM
Scanning not only option
It is important to add that, it is not needed to scan to detect a vulnerability. Too many orgs rely on scanning as the primary method. Use scanning to know your asset, match up against a Vulnerability Intelligence Feed, and then drive your VM based on risk. You don't need to patch all vulns at once, but you do need to know about all the vulns that impact your asset so you can make a risk based decision.


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
Improving Enterprise Cybersecurity With XDR
Enterprises are looking at eXtended Detection and Response technologies to improve their abilities to detect, and respond to, threats. While endpoint detection and response is not new to enterprise security, organizations have to improve network visibility, expand data collection and expand threat hunting capabilites if they want their XDR deployments to succeed. This issue of Tech Insights also includes: a market overview for XDR from Omdia, questions to ask before deploying XDR, and an XDR primer.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-2287
PUBLISHED: 2022-07-02
Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.
CVE-2022-34911
PUBLISHED: 2022-07-02
An issue was discovered in MediaWiki before 1.35.7, 1.36.x and 1.37.x before 1.37.3, and 1.38.x before 1.38.1. XSS can occur in configurations that allow a JavaScript payload in a username. After account creation, when it sets the page title to "Welcome" followed by the username, the usern...
CVE-2022-34912
PUBLISHED: 2022-07-02
An issue was discovered in MediaWiki before 1.37.3 and 1.38.x before 1.38.1. The contributions-title, used on Special:Contributions, is used as page title without escaping. Hence, in a non-default configuration where a username contains HTML entities, it won't be escaped.
CVE-2022-34913
PUBLISHED: 2022-07-02
** DISPUTED ** md2roff 1.7 has a stack-based buffer overflow via a Markdown file containing a large number of consecutive characters to be processed. NOTE: the vendor's position is that the product is not intended for untrusted input.
CVE-2022-2286
PUBLISHED: 2022-07-02
Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.