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
Department Of Energy Confirms Data Breach
Newest First  |  Oldest First  |  Threaded View
kbuchs559
50%
50%
kbuchs559,
User Rank: Apprentice
2/6/2013 | 8:48:15 PM
re: Department Of Energy Confirms Data Breach
The Article states:
Interestingly, the DOE memo urged all employees "to help minimize impacts and reduce any potential risks" by encrypting all files and emails that contained PII, "including files stored on hard drives or on the shared network." That request suggests that the agency has yet to implement or mandate the use of full-disk encryption tools for all employees and contractors.

I disagree with the conclusion. Full-disk encryption protects the contents should someone steal the disk drive from the machine. It does not protect the contents of the filesystem if that computer is running and a adversary obtains network access. File encryption is different and would require entering a password to open the files.
MyW0r1d
50%
50%
MyW0r1d,
User Rank: Apprentice
2/6/2013 | 4:53:12 PM
re: Department Of Energy Confirms Data Breach
Any network can be the objective of successful attacks (DDoS or infiltration hacks) and government agencies would top the list. What makes the difference as the author states is how it is handled. In separate article on the same incident it was stated some 14 servers and a couple of dozen workstations were compromised. The only response of DoE in that article was a non chalant dismissal of it as only PII not classified information. That seems to be a lot of PII and personal information on government systems while sensitive information does not necessarily coincide with classified. I put it in the same category as the ATF CIO that has made a 2+ year focus on mobility devices (putting iPhones in the hands of agents) while they are still using microfiche for tracking weapons sales (like the Sandy Hook variety). My point is there may be more govt CIOs whose prioritization of needs may beg for re-evaluation than just DoE when fundamental services are sacrificed to cutting edge systems with limited ROI.
Andrew Hornback
50%
50%
Andrew Hornback,
User Rank: Apprentice
2/6/2013 | 4:38:58 AM
re: Department Of Energy Confirms Data Breach
"Why might attackers have targeted PII for agency employees and contractors?" Isn't the quite obvious answer here, given what the Department of Energy does, to sell that information on the black market? Not just for identity theft, that's somewhat low hanging fruit - but wouldn't this kind of information make it a lot easier for "unfriendly" forces to know who to target (and how to target them) in order to get information?

To think that someone would go to these lengths just to rip someone off and get a new flat screen TV is somewhat ludicrous, and akin to thinking that the world is a safe, sanitary place. I can think of any number of organizations that would be interested in "having a cup of coffee" with properly placed folks at the DoE.

Bottom line - DoE's CIO and/or CISO need to go and the organization needs to seriously re-evaluate how they handle information security.

How old is FIPS 140-2 again? Exactly.

Andrew Hornback
InformationWeek Contributor


COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...