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?
Higher Education: 15 Books to Help Cybersecurity Pros Be Better
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/12/2018
Worst Password Blunders of 2018 Hit Organizations East and West
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/12/2018
2019 Attacker Playbook
Ericka Chickowski, Contributing Writer, Dark Reading,  12/14/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
10 Best Practices That Could Reshape Your IT Security Department
This Dark Reading Tech Digest, explores ten best practices that could reshape IT security departments.
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-2018-20173
PUBLISHED: 2018-12-17
Zoho ManageEngine OpManager 12.3 before 123238 allows SQL injection via the getGraphData API.
CVE-2017-18352
PUBLISHED: 2018-12-17
Error reporting within Rendertron 1.0.0 allows reflected Cross Site Scripting (XSS) from invalid URLs.
CVE-2017-18353
PUBLISHED: 2018-12-17
Rendertron 1.0.0 includes an _ah/stop route to shutdown the Chrome instance responsible for serving render requests to all users. Visiting this route with a GET request allows any unauthorized remote attacker to disable the core service of the application.
CVE-2017-18354
PUBLISHED: 2018-12-17
Rendertron 1.0.0 allows for alternative protocols such as 'file://' introducing a Local File Inclusion (LFI) bug where arbitrary files can be read by a remote attacker.
CVE-2017-18355
PUBLISHED: 2018-12-17
Installed packages are exposed by node_modules in Rendertron 1.0.0, allowing remote attackers to read absolute paths on the server by examining the "_where" attribute of package.json files.