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
Security Orchestration Fine-Tunes the Incident Response Process
Oldest First  |  Newest First  |  Threaded View
treyka
treyka,
 User Rank: Apprentice
6/12/2017 | 9:19:32 AM
OpenC2 is a rather glaring omission from this article
While a well-written article, the failure to mention the work of the OpenC2 consortium developing a vendor-neutral standard for the mitigating actions and playbooks that drive security orchestration was surely an oversight.

The OpenC2 work represents a long-standing collaboration by a large number of vendors, enterprises, government agencies, and academic institutions. This effort has reached a sufficient level of maturity that the consortium recently moved their work into an OASIS technical committee in order to promulgate an official open standard to accelerate security automation in an interoperable fashion.

Because DarkReading's comment system doesn't allow urls in comments, herewith useful references:

* openc2[dot]org

* www[dot]oasis-open[dot]org/apps/org/workgroup/openc2/#overview
RetiredUser
RetiredUser,
 User Rank: Ninja
6/12/2017 | 11:56:38 AM
Re: OpenC2 is a rather glaring omission from this article
The OASIS TC Inaugural Meeting will be an important step in seeing OpenC2 move forward and appear in more articles like those found here on DR.  As a longtime FOSS user and occasional developer, the potential for OpenC2 appears solid.  I think when more projects start appearing with POC setups that include pentesting kits like BackBox on one end, and OpenC2 with various security tools on the other, we can really start pointing to OpenC2 as the future of security automation management. 

The problem I have with massive commercial systems is the lack of availability to lab testers and FOSS developers to really put them to task and see what they can do.  Too many of these expensive "Enterprise" systems come at such expense and require massive resources to properly deploy; not to mention the amount of time needed to even see results that might reflect well on what the product offers.  OpenC2 represents hope to move in the other direction.

Appreciate you dropping this reference.  And, I was checking out CybOX before it integrated with STIX, and that's how I first heard about OpenC2 when papers started popping up talking about CybOX and STIX in relation to OpenC2.  Anyone with awareness of this whole body of code should be looking at OpenC2 closely over the next year...


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
The Promise and Reality of Cloud Security
Cloud security has been part of the cybersecurity conversation for years but has been on the sidelines for most enterprises. The shift to remote work during the COVID-19 pandemic and digital transformation projects have moved cloud infrastructure front-and-center as enterprises address the associated security risks. This report - a compilation of cutting-edge Black Hat research, in-depth Omdia analysis, and comprehensive Dark Reading reporting - explores how cloud security is rapidly evolving.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-43762
PUBLISHED: 2023-02-08
Lack of verification in B&R APROL Tbase server versions < R 4.2-07 may lead to memory leaks when receiving messages
CVE-2022-43763
PUBLISHED: 2023-02-08
Insufficient check of preconditions could lead to Denial of Service conditions when calling commands on the Tbase server of B&R APROL versions < R 4.2-07.
CVE-2022-43764
PUBLISHED: 2023-02-08
Insufficient validation of input parameters when changing configuration on Tbase server in B&R APROL versions < R 4.2-07 could result in buffer overflow. This may lead to Denial-of-Service conditions or execution of arbitrary code.
CVE-2022-43765
PUBLISHED: 2023-02-08
B&R APROL versions < R 4.2-07 doesn’t process correctly specially formatted data packages sent to port 55502/tcp, which may allow a network based attacker to cause an application Denial-of-Service.
CVE-2022-2094
PUBLISHED: 2023-02-08
The Yellow Yard Searchbar WordPress plugin before 2.8.2 does not escape some URL parameters before outputting them back to the user, leading to Reflected Cross-Site Scripting