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%
inShareLink => http://www.darkreading.com/compliance-is-a-start-not-the-end/v/d-id/1316739inSite => darkreading

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?
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
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-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.