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.

Risk //

Compliance

Compliance Is A Start, Not The End

100%
0%

Regulatory compliance efforts may help you get a bigger budget and reach a baseline security posture. But "compliant" does not necessarily mean "secure."

Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
The Integrator
50%
50%
The Integrator,
User Rank: Apprentice
6/29/2015 | 3:55:49 AM
We need to move to continuous adaptive compliance
Current compliance regiemes are labourious, provide a snapshot of compliance and offer little value for the effort.

We need to move to automation where evidence is gathered automatiacally and once for every aspect we need to report on, so we are not manually taking screenshots for PCI, SOX, HIPPA etc.  Setup once, gather as needed and report non compliance for investigation, that way you will be as close to full compliance most of the time.

Compliance does not equal security
shalivaha
50%
50%
shalivaha,
User Rank: Apprentice
6/8/2015 | 2:59:37 AM
Re: Pending Review
yes its not the end
ramesh kumar13
50%
50%
ramesh kumar13,
User Rank: Apprentice
6/8/2015 | 2:35:56 AM
Re: Checkbox security
Noble thoughts, to be sure. But who in the Dark Reading community can honestly say that their company does not practice check box security at least some of the time?
UTIWARI
50%
50%
UTIWARI,
User Rank: Apprentice
10/24/2014 | 12:13:54 PM
Re: Checkbox security
While "checking the box" is often a requirement and companies cannot get away with not focusing on "checking the box", it may be helpful to include "checking the box" as part of overall risk management strategy and look at the compliance activity from risk lense and not overlook other aspects that may take you beyond checkbox thinking and actually take care of risks that your company is better off not being exposed to.
Marilyn Cohodas
100%
0%
Marilyn Cohodas,
User Rank: Strategist
10/22/2014 | 8:46:14 AM
Checkbox security
Noble thoughts, to be sure. But who in the Dark Reading community can honestly say that their company does not practice check box security at least some of the time? My guess -- it's closer to 50 percent of checkbox security practices.  Am I right or wrong?
97% of Americans Can't Ace a Basic Security Test
Steve Zurier, Contributing Writer,  5/20/2019
How Security Vendors Can Address the Cybersecurity Talent Shortage
Rob Rashotte, VP of Global Training and Technical Field Enablement at Fortinet,  5/24/2019
TeamViewer Admits Breach from 2016
Dark Reading Staff 5/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-7068
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7069
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have a type confusion vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7070
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7071
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.
CVE-2019-7072
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .