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

Feds Issue Government Teleworker Security Guidelines

OMB rules apply to departments, agencies that must secure access to wireless networks and IT systems when employees work remotely.

Inside DHS' Classified Cyber-Coordination Headquarters
(click image for larger view)
Slideshow: Inside DHS' Classified Cyber-Coordination Headquarters
Protection of external IT systems and safeguarding wireless and other telecommunications capabilities that federal teleworkers use are among security guidelines the Office of Management and Budget (OMB) has stipulated as part of the Obama administration's telework policy.

In a memo this week, the OMB released the guidelines to support activity made possible by the Federal Telework Act of 2010, signed in December by President Obama to codify an activity the federal government already was engaged in and beginning to embrace on a wider scale. The memo was directed at the heads of executive departments and agencies.

"Telework ... provides federal employees the ability to continue working during inclement weather, emergencies, or situations that may disrupt normal operations," OMB Director Jacob Lew wrote in the memo. "However, telework is only as effective as the technologies used to support it, which is why it is critical for agencies to take immediate action to ensure that their employees are properly equipped.

The two-page memo on security guidelines are a complement to a 41-page document of overall teleworking guidelines the OMB released in April to inform departments and agencies how to manage employees who are eligible for telework and choose to do so. That document put the task of coming up with security guidelines in the hands of the Department of Homeland Security and the National Institute of Standards and Technology (NIST).

Indeed, as part of the guidelines spelled out in the memo, agencies and departments also must comply with the requirements of the Federal Information Security Management Act of 2002, better known as FISMA, for which NIST develops standards and guidelines.

In addition to securing wired and wireless networks teleworkers might use while performing their federal duties, agencies also must address several other issues to ensure teleworkers are performing their tasks securely.

Agencies and departments must control access to agency information and IT systems while employees telework, and also protect agency information--including personally identifiable information--and IT systems, according to the memo.

Other guidelines they must follow include limiting the introduction of vulnerabilities and preventing inappropriate use of official time or resources that violate federal policies regarding the viewing of pornography--including child pornography--while at work.

To ensure the implementation of these policies, agency CIOS must appoint a technical point of contact to the DHS, according to the OMB.

Black Hat USA 2011 presents a unique opportunity for members of the security industry to gather and discuss the latest in cutting-edge research. It happens July 30-Aug. 4 in Las Vegas. Find out more and register.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
SOC 2s & Third-Party Assessments: How to Prevent Them from Being Used in a Data Breach Lawsuit
Beth Burgin Waller, Chair, Cybersecurity & Data Privacy Practice , Woods Rogers PLC,  12/5/2019
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
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-2019-19702
PUBLISHED: 2019-12-10
The modoboa-dmarc plugin 1.1.0 for Modoboa is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this to perform a denial of service against the DMARC reporting functionality, such as by referencing the /dev/random file within XML do...
CVE-2019-19703
PUBLISHED: 2019-12-10
In Ktor through 1.2.6, the client resends data from the HTTP Authorization header to a redirect location.
CVE-2012-1577
PUBLISHED: 2019-12-10
lib/libc/stdlib/random.c in OpenBSD returns 0 when seeded with 0.
CVE-2012-5620
PUBLISHED: 2019-12-10
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
CVE-2013-1689
PUBLISHED: 2019-12-10
Mozilla Firefox 20.0a1 and earlier allows remote attackers to cause a denial of service (crash), related to event handling with frames.