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

2/26/2008
01:49 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Surprise, Surprise. Federal Agencies Not Protecting The Information They Collect About You

There are many policies, mandates, and laws that govern personally identifiable and financial information for federal agencies. So just how many federal agencies are living up to their responsibilities?

There are many policies, mandates, and laws that govern personally identifiable and financial information for federal agencies. So just how many federal agencies are living up to their responsibilities?You guessed it: not many.

When it comes to maintaining the privacy of information government agencies collect about U.S. citizenry, there are two overarching laws. These are the Privacy Act of 1974 as well as the E-Government Act of 2002. Each of these laws mandate that federal agencies protect personal information.

Other laws and mandates that come into play, depending on the nature of the agency and the information stored, include the Federal Information Security Management Act of 2002, aka FISMA -- which sets forth a good baseline for security policies; the Health Information Portability and Accountability Act, aka HIPAA; as well as the California Database Breach Disclosure law, which is largely known as SB 1386,and now similar laws are in force in more than 40 other states.

You'd think federal agencies would have clearly heard the message: citizens want their personal information maintained securely and responsibly. And so does the legislature. If they've heard the message, they certainly haven't listened. If there's one area where the federal government could set an example, you'd think it would be in implementing solid IT security. But it hasn't set such an example.

That's why in 2006, and once again last year, the Office of Management and Budget recapped federal agency IT security and privacy responsibilities that should be followed.

Unfortunately, here are the findings from the latest Government Accountability Office report on the status of federal agencies when it comes to protecting your personal information:

Of 24 major agencies, 22 had developed policies requiring personally identifiable information to be encrypted on mobile computers and devices. Fifteen of the 24 agencies had policies to use a "time-out" function for remote access and mobile devices, requiring user re-authentication after 30 minutes of inactivity.

Fewer agencies (11) had established policies to log computer-readable data extracts from databases holding sensitive information and erase the data within 90 days after extraction. Several agencies indicated that they were researching technical solutions to address these issues.

At first blush, these results might not seem so bad. After all, 22 of 24 agencies have developed "polices requiring personally identifiable information to be encrypted on mobile computers and devices."

That's a start. But the devil is in the implementation and enforcement of polices. Anyone can set a policy requiring data be encrypted. Just as anyone can set a policy to live within a budget, lose weight, quit smoking, or start exercising. Follow-through is the tough part.

And that's the rub here, according to the GAO: "Gaps in their [federal agency] policies and procedures reduced agencies' ability to protect personally identifiable information from improper disclosure."

Also, I'd like to pose a question: Why does citizen personally identifiable information need be on a notebook or "other mobile device" at all?

Is it too much to ask, when working with sensitive information, that workers and consultants actually sit at a workstation, in an office, where the network and system can be kept highly secured? And if they need remote access, why not use a thin device so the data stays in the database, and isn't left at a worksite ... or on a table in Starbucks.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
Breaches Are Inevitable, So Embrace the Chaos
Ariel Zeitlin, Chief Technology Officer & Co-Founder, Guardicore,  11/13/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-2916
PUBLISHED: 2019-11-15
qtnx 0.9 stores non-custom SSH keys in a world-readable configuration file. If a user has a world-readable or world-executable home directory, another local system user could obtain the private key used to connect to remote NX sessions.
CVE-2019-12757
PUBLISHED: 2019-11-15
Symantec Endpoint Protection (SEP), prior to 14.2 RU2 & 12.1 RU6 MP10 and Symantec Endpoint Protection Small Business Edition (SEP SBE) prior to 12.1 RU6 MP10d (12.1.7510.7002), may be susceptible to a privilege escalation vulnerability, which is a type of issue whereby an attacker may attempt t...
CVE-2019-12758
PUBLISHED: 2019-11-15
Symantec Endpoint Protection, prior to 14.2 RU2, may be susceptible to an unsigned code execution vulnerability, which may allow an individual to execute code without a resident proper digital signature.
CVE-2019-12759
PUBLISHED: 2019-11-15
Symantec Endpoint Protection Manager (SEPM) and Symantec Mail Security for MS Exchange (SMSMSE), prior to versions 14.2 RU2 and 7.5.x respectively, may be susceptible to a privilege escalation vulnerability, which is a type of issue whereby an attacker may attempt to compromise the software applicat...
CVE-2019-18372
PUBLISHED: 2019-11-15
Symantec Endpoint Protection, prior to 14.2 RU2, may be susceptible to a privilege escalation vulnerability, which is a type of issue whereby an attacker may attempt to compromise the software application to gain elevated access to resources that are normally protected from an application or user.