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
NASA Investigating Breach That Exposed PII on Employees, Ex-Workers
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
NathanDavidson
50%
50%
NathanDavidson,
User Rank: Moderator
1/8/2019 | 4:15:44 AM
Background checks
It is scary to know that data breaches within even the most successful organisations have become ever so common within the recent past. In majority of such cases, an internal breach is to be blamed which simply means that the organisation had committed a mistake during their recruitment drive. Every single employee ought to be sucritinized in terms of their background checks just to see if there's any potential amongst any of the workers to commit crimes like data breaches.
CameronRobertson
50%
50%
CameronRobertson,
User Rank: Moderator
1/3/2019 | 6:33:59 AM
would think that personnel working
You would think that personnel working in a facility with that kind of security especially with the amount of sensitive information going around that place, would know better about how to protect themselves from being the target of attack when it comes to external forces trying to attack the facility for the data in storage... Seems like they still have a lot to learn...
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
12/26/2018 | 12:55:31 PM
Re: inb4
cybersecurity isn't rocket science" joke Agree. Hart to argue with it.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
12/26/2018 | 12:54:06 PM
Re: Reasons why these things continue to happen at Federal Agencies
Meaning, cut, cut, cut even though IT is vital to the day to day operations & success of the organization. I think we can certainly cut and stay secure. It is just changing mindset that security is part of daily operation.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
12/26/2018 | 12:52:50 PM
Re: Reasons why these things continue to happen at Federal Agencies
Many organizations view IT as non revenue generating and thus treat them in that manner. That would be true. Organizations would try to avoid expenses for security as much as possible.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
12/26/2018 | 12:51:49 PM
Re: Reasons why these things continue to happen at Federal Agencies
They only care about fulfilling their core mission. I assume they are blinded by the regulations bit they do not have to obey obviously.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
12/26/2018 | 12:50:31 PM
Re: Reasons why these things continue to happen at Federal Agencies
because their superiors do not care about security unless a breach is publicized and they become embarrassed Yes, this represents a cultural issue in the agencies.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
12/26/2018 | 12:49:23 PM
Re: Reasons why these things continue to happen at Federal Agencies
Even when there are qualified IT security professionals, they are often overruled in their attempts to increase security, I would guess this might be the norm. They do not want to spend money on security most likely as it gests expensive in most cases.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
12/26/2018 | 12:47:59 PM
Re: Reasons why these things continue to happen at Federal Agencies
Also, the pay structures of the federal government do not generally allow the agencies to pay what they need to pay for qualified IT security personnel. If I guess I would guess that is is less about money/personel than the culture of the agencies.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
12/26/2018 | 12:46:28 PM
Re: Reasons why these things continue to happen at Federal Agencies
Federal Agencies are loathe to spend money on IT security because it is not central to their mission. That is true too. It should be part of their mission definition in my view.
Page 1 / 2   >   >>


Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5216
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.9.0, 5.2.0, and 6.3.0. If user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection. Upon seei...
CVE-2020-5217
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.8.0, 5.1.0, and 6.2.0. If user-supplied input was passed into append/override_content_security_policy_directives, a semicolon could be injected leading to directive injection. This could b...
CVE-2020-5223
PUBLISHED: 2020-01-23
In PrivateBin versions 1.2.0 before 1.2.2, and 1.3.0 before 1.3.2, a persistent XSS attack is possible. Under certain conditions, a user provided attachment file name can inject HTML leading to a persistent Cross-site scripting (XSS) vulnerability. The vulnerability has been fixed in PrivateBin v1.3...
CVE-2019-20399
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
CVE-2020-7915
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.