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.

Comments
Why Are Security Pros Blas About Compliance?
Newest First  |  Oldest First  |  Threaded View
Page 1 / 3   >   >>
aws0513
aws0513,
User Rank: Ninja
9/9/2014 | 10:48:07 AM
Re: The culture of the organization.
Those are some of the big regulatory players for sure.

If there were anything to add, specifically in the US, it would be state laws or regulations.
More and more I am running into situations where states have established statutory requirements for the protection and handling of specific categories of data that may exceed or augments some of the regulatory directives you listed.

So many fingers in the regulatory security jar. 

Not complaining...  any regulatory requirement from any angle helps in the effort to gain resources and support for security controls that are necessary.  But the complexity of bringing all of the requirements together and addressed accordingly can be daunting at times.
GonzSTL
GonzSTL,
User Rank: Ninja
9/8/2014 | 4:30:06 PM
Re: The culture of the organization.
I think enforcement is as follows:

HIPAA - Office of Civil Rights, Department of Health and Human Services
HITECH - Office of Civil Rights, Department of Health and Human Services
FERPA - Family Policy Compliance Office, Department of Education
FOIA  - Federal Court, Department of Justice (states have similar regulations)
Dodd-Frank - Securities and Exchange Commission
FINRA - FINRA (check a ruling by the Court of Appeals for the Second Circuit)
FRCP - Federal Court, Department of Justice
MiFID - European Union Countries
gwavajeff
gwavajeff,
User Rank: Apprentice
9/8/2014 | 4:00:04 PM
Re: The culture of the organization.
The entities involved in the investigations and litigations are varied, but the top three were the Department of Justice (DOJ), the Securities and Exchange Commission (SEC), and the Environmental Protection Agency (EPA).

Healthcare, technology/communications, and energy companies were the prime target of the DOJ. Surprisingly, energy companies were two times more likely than financial services to be the primary target of the SEC. Energy companies were also the target of the EPA, with manufacturing also having been a heavy target.

Rounding out the top ten list of agencies targeting businesses in regulatory investigations was the State Attorney General, Occupational Safety and Health Administration (OSHA), Financial Industry Regulatory Authority (FINRA), the Internal Revenue Service (IRS), the US Attorney's Office, the Food and Drug Administration (FDA), and the State District or County Attorney. 

I have a whole post about the issue on our blog, with links to the surveys I mentioned, and go into more, but I not trying to be spammy. First half of username dot com slash blog
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
9/8/2014 | 3:31:25 PM
Re: The culture of the organization.
Who enforces there regulations @gwavajeff and do they have any teeth?
gwavajeff
gwavajeff,
User Rank: Apprentice
9/8/2014 | 1:49:07 PM
Re: The culture of the organization.
I know you were focused on a couple specific compliance regs. I wanted to point out that there are a number of other compliance regulations of which many organizations are not aware. Most notably Federal Rules of Civil Procedure (FRCP).  The FRCP requires companies to archive their electronic communications, which most assume is email, but has now expanded to mobile device messages (SMS/MMS), instant messaging, as well as employee's social media messages. 

Regulatory and investigation litigations have more than doubled in the last year. According to ESG almost half of businesses surveyed had an eDiscovery request in the last 12-months, and Gartner expects that to be around 75% by the end of the year. 

The Norton Rose Fulbright Annual Litigation Trends Survey found that regulatory litigations and investigations are the largest increase on concern for respondends in the last year, and regulatory litigation over the last year has more than doubled. 

Here are a few more compliance regulations for those that are interested:

Financial Industries Regulations
  • FINRA, SEC, MiFID and FSA government rules
  • Dodd-Frank Act (which requires that you produce communications within 72 hours of an auditor request)

Governmental Entities Regulations
  • The Freedom of Information Act, "Sunshine Laws" (vary from state to state)

Education Institution Regulations
  • Family Education Rights and Privacy Act (FERPA)

Healthcare Facility Regulations
  • HIPAA, HITECH

 
GonzSTL
GonzSTL,
User Rank: Ninja
8/29/2014 | 3:56:38 PM
Re: More Details Please
Years ago, the hot topic was to align IT objectives to the goals of an organization. That remains true today, but in addition, security must also align with the goals of the organization. This is more difficult a task because most effects of security are so intangible. In reality, security aligns with IT goals, which in turn align with organizational goals. It really boils down to communicationg security objectives not just in way fit that is for executive consumption, but also to show how security itself aligns and supports organizational goals. To be fair, this is not a one sided task because in order to succeed, executive management must be receptive to the message. Again, in today's connected sociery, with the almost daily news of breaches, executives must listen.
Robert McDougal
Robert McDougal,
User Rank: Ninja
8/29/2014 | 2:52:17 PM
Re: More Details Please
In my experience it boils down to money.  We have spent all of this money to become compliant, why would we want to spend more on a line item that does not add to the bottom line.  Executives must be educated to the value of security and not just the necissity of it.
RyanSepe
RyanSepe,
User Rank: Ninja
8/29/2014 | 2:42:35 PM
Re: More Details Please
@GonzSTL, I have brought this fact to the surface countless times and agree with you whole heartedly. This is why the need for a CISO/CSO is so important. They need to be the drivers of forcing policy, improving standards, and things of that nature to the VP's and Execs. 
Ed Telders
Ed Telders,
User Rank: Apprentice
8/29/2014 | 1:14:38 PM
Re: The culture of the organization.
Actually PCI DSS is a standard and not a regulation at all.  In some ways though, it has bigger impacts.  This standard is a requirement because of contractual agreements your organization has agreed to for card processing.  There are a few jurisdictions that have mandated PCI compliance to conduct business but they are only a few.  Compliance with PCI is a business and contractual issue.  They have the impact of fines, sanctions, and public disclosure of PCI compliance status. 

All good, still needs to be done, but let's be clear this is not a regulation. 
GonzSTL
GonzSTL,
User Rank: Ninja
8/29/2014 | 12:42:24 PM
Re: More Details Please
I agree, Tim; security pros are not necessarily blase' about compliance. in fact, I'm sure that the vast majority of them take compliance and security very seriously. In my opinion, the biggest challenge they face can be summed up in this scenario:

Executive: Are all the boxes checked?

Security: Yes

Executive: Then we are done.

Security: But there is so much more that we should do to enhance security!

Executive: We are compliant, and that's all we are required to do. We have other priorities.

How many of you have experienced this, or something similar? I know I have, and in more than one instance. The really sad thing about all this whole compliance/security thing is that if an organization cultivates a culture that includes secure practices in all aspects of its business, they will be compliant. When I examine the requirements of standards like PCI-DSS and the security and privacy sections of HIPAA, I cannot help but note that these are simply known security practices - none of them are novel ideas! Furthermore, if a CEO or CIO or any other C-level person does not promote this type of culture, then I submit that that executive does not have the best security interests of the organization at heart, and by extention, place their organizations in jeopardy. I admit that most C level executives are not security or even tech savvy, but in today's connected environment, they must wake up and smell the coffee.
Page 1 / 3   >   >>


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 10 Most Impactful Types of Vulnerabilities for Enterprises Today
Managing system vulnerabilities is one of the old est - and most frustrating - security challenges that enterprise defenders face. Every software application and hardware device ships with intrinsic flaws - flaws that, if critical enough, attackers can exploit from anywhere in the world. It's crucial that defenders take stock of what areas of the tech stack have the most emerging, and critical, vulnerabilities they must manage. It's not just zero day vulnerabilities. Consider that CISA's Known Exploited Vulnerabilities (KEV) catalog lists vulnerabilitlies in widely used applications that are "actively exploited," and most of them are flaws that were discovered several years ago and have been fixed. There are also emerging vulnerabilities in 5G networks, cloud infrastructure, Edge applications, and firmwares to consider.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-1142
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use URL decoding to retrieve system files, credentials, and bypass authentication resulting in privilege escalation.
CVE-2023-1143
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use Lua scripts, which could allow an attacker to remotely execute arbitrary code.
CVE-2023-1144
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 contains an improper access control vulnerability in which an attacker can use the Device-Gateway service and bypass authorization, which could result in privilege escalation.
CVE-2023-1145
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 are affected by a deserialization vulnerability targeting the Device-DataCollect service, which could allow deserialization of requests prior to authentication, resulting in remote code execution.
CVE-2023-1655
PUBLISHED: 2023-03-27
Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.4.0.