One Article Review
| Source |  CSO |
|---|---|
| Identifiant | 6622447 |
| Date de publication | 2022-08-30 02:00:00 (vue: 2022-08-30 10:05:43) |
| Titre | Key takeaways from the Open Cybersecurity Schema Format |
| Texte | One of the most pervasive challenges in the current cybersecurity environment is an overabundance of tooling vendors, all of which produce telemetry or data, often in their own native or nuanced schema or format. As cybersecurity's visibility has risen in organizations, so has the number of cybersecurity vendors and tools that teams need to integrate, implement and govern. Cybersecurity professionals must spend time getting tools to work together as a cohesive portfolio, which detracts from their efforts to identify and address cybersecurity vulnerabilities and threats.The problem isn't going unnoticed. Recently Amazon Web Services (AWS) along with other leaders such as Splunk, CrowdStrike, Palo Alto, Rapid7, and JupiterOne announced the release of the Open Cybersecurity Schema Framework (OCSF) project. The announcement acknowledges the problem of security professionals needing to wrestle with proprietary data formats and outputs rather than their actual roles of risks and threats. This is problematic given the industry is already facing significant workforce challenges, burnout and fatigue. By standardizing on security product schemas and formats, security practitioners can spend more time addressing threats that pose risks to organizations.To read this article in full, please click here |
| Envoyé | Oui |
| Condensat | acknowledges actual address addressing all along already alto amazon announced announcement article aws burnout can challenges click cohesive crowdstrike current cybersecurity data detracts efforts environment facing fatigue format formats framework from full getting given going govern has here identify implement industry integrate isn jupiterone key leaders more most must native need needing nuanced number ocsf often one open organizations other outputs overabundance own palo pervasive please portfolio pose practitioners problem problematic produce product professionals project proprietary rapid7 rather read recently release risen risks roles schema schemas security services significant spend splunk standardizing such takeaways teams telemetry than threats time together tooling tools unnoticed vendors visibility vulnerabilities web which work workforce wrestle |
| Tags | Guideline |
| Stories | |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.