Einstein (US-CERT program)

EINSTEIN (also known as the EINSTEIN Program) was originally an intrusion detection system that monitors the network gateways of government departments and agencies in the United States for unauthorized traffic. The software was developed by the United States Computer Emergency Readiness Team (US-CERT),[1] which is the operational arm of the National Cyber Security Division[2] (NCSD) of the United States Department of Homeland Security (DHS).[3] The program was originally developed to provide "situational awareness" for the civilian agencies. While the first version examined network traffic and subsequent versions examined content,[4] the current version of EINSTEIN is significantly more advanced.

For other uses, see Einstein (disambiguation).
EINSTEIN
Developer(s)US-CERT
Initial release2004
Typenetwork security and computer security
WebsiteAnalytical Tools and Programs at US-CERT for government users

Mandate
The National Strategy to Secure Cyberspace (February 2003) featured the new cabinet-level United States Department of Homeland Security as the lead agency protecting IT.[5]

EINSTEIN is the product of U.S. congressional and presidential actions of the early 2000s including the E-Government Act of 2002 which sought to improve U.S. government services on the Internet.

So where did the name EINSTEIN come from? During the initial formation of the program, the program was referred to as SAP which stood for the Situational Awareness Program. Unfortunately, SAP is not the best acronym for a government cybersecurity program and there was a need to change this to something different. Hanging in Rob Pate's office at GSA Building in Washington, D.C. at 7th and D Street (initial offices of both FedCIRC and the newly formed US-CERT) was a poster of Albert Einstein. The team was looking for a new name and the decision to use the name EINSTEIN was made by Rob Pate, Sean McAllister, and Mike Witt.

EINSTEIN's mandate originated in the Homeland Security Act and the Federal Information Security Management Act, both in 2002, and the Homeland Security Presidential Directive (HSPD) 7,[1] which was issued on December 17, 2003.[6]

The Federal Computer Incident Response Capability (FedCIRC) was one of four watch centers that were protecting federal information technology[7] when the E-Government Act of 2002 designated it the primary incident response center.[8] With FedCIRC at its core, US-CERT was formed in 2003 as a partnership between the newly created DHS and the CERT Coordination Center which is at Carnegie Mellon University and funded by the U.S. Department of Defense.[7] US-CERT delivered EINSTEIN to meet statutory and administrative requirements that DHS help protect federal computer networks and the delivery of essential government services.[1] EINSTEIN was implemented to determine if the government was under cyber attack. EINSTEIN did this by collecting flow data from all civilian agencies and compared that flow data to a baseline.

  1. If one Agency reported a cyber event, the 24/7 Watch at US-CERT could look at the incoming flow data and assist resolution.
  2. If one Agency was under attack, US-CERT Watch could quickly look at other Agency feeds to determine if it was across the board or isolated.

On November 20, 2007, "in accordance with" an Office of Management and Budget (OMB) memo,[9] EINSTEIN version 2 was required for all federal agencies, except the Department of Defense and United States Intelligence Community agencies in the executive branch.[10]

Adoption

EINSTEIN was deployed in 2004[1] and until 2008 was voluntary.[11] By 2005, three federal agencies participated and funding was available for six additional deployments. By December 2006, eight agencies participated in EINSTEIN and by 2007, DHS itself was adopting the program department-wide.[12] By 2008, EINSTEIN was deployed at fifteen[13] of the nearly six hundred agencies, departments and Web resources in the U.S. government.[14]

Features

When it was created, EINSTEIN was "an automated process for collecting, correlating, analyzing, and sharing computer security information across the Federal civilian government."[1] EINSTEIN does not protect the network infrastructure of the private sector.[15] As described in 2004, its purpose is to "facilitate identifying and responding to cyber threats and attacks, improve network security, increase the resiliency of critical, electronically delivered government services, and enhance the survivability of the Internet."[1]

EINSTEIN was designed to resolve the six common security weaknesses[1] that were collected from federal agency reports and identified by the OMB in or before its report for 2001 to the U.S. Congress.[16] In addition, the program addresses detection of computer worms, anomalies in inbound and outbound traffic, configuration management as well as real-time trends analysis which US-CERT offers to U.S. departments and agencies on the "health of the Federal.gov domain".[1] EINSTEIN was designed to collect session data including:[1]

US-CERT may ask for additional information in order to find the cause of anomalies EINSTEIN finds. The results of US-CERT's analysis are then given to the agency for disposition.[1]

EINSTEIN 2

During EINSTEIN 1, it was determined that the civilian agencies did not know the entirety of what their registered IPv4 space included. This was obviously a security concern. Once an Agency's IPv4 space was validated, it was immediately clear that the Agency had more external Internet Connections or Gateways than could be reasonably instrumented and protected. This gave birth to the OMB's TIC, Trusted Internet Connections" Initiative. Three constraints on EINSTEIN that the DHS is trying to address are the large number of access points to U.S. agencies, the low number of agencies participating, and the program's "backward-looking architecture".[17] An OMB "Trusted Internet Connections" initiative[9] was expected to reduce the government's 4,300 access points to 50 or fewer by June 2008.[18][19] After agencies reduced access points by over 60% and requested more than their target, OMB reset their goal to the latter part of 2009 with the number to be determined.[19] A new version of EINSTEIN was planned to "collect network traffic flow data in real time and also analyze the content of some communications, looking for malicious code, for example in e-mail attachments."[20] The expansion is known to be one of at least nine measures to protect federal networks.[21]

The new version, called EINSTEIN 2, will have a "system to automatically detect malicious network activity, creating alerts when it is triggered".[22] EINSTEIN 2 will use "the minimal amount" necessary of predefined attack signatures which will come from internal, commercial and public sources. The EINSTEIN 2 sensor monitors each participating agency's Internet access point, "not strictly...limited to" Trusted Internet Connections, using both commercial and government-developed software.[23] EINSTEIN could be enhanced to create an early warning system to predict intrusions.[17]

US-CERT may share EINSTEIN 2 information with "federal executive agencies" according to "written standard operating procedures" and only "in a summary form". Because US-CERT has no intelligence or law enforcement mission it will notify and provide contact information to "law enforcement, intelligence, and other agencies" when an event occurs that falls under their responsibility.[23]

EINSTEIN 3

Version 3.0 of EINSTEIN has been discussed to prevent attacks by "shoot[ing] down an attack before it hits its target."[24] The NSA is moving forward to begin a program known as “EINSTEIN 3,” which will monitor “government computer traffic on private sector sites.” (AT&T is being considered as the first private sector site.) The program plan, which was devised under the Bush administration, is controversial, given the history of the NSA and the warrantless wiretapping scandal. Many DHS officials fear that the program should not move forward because of “uncertainty about whether private data can be shielded from unauthorized scrutiny.”[25] Some believe the program will invade the privacy of individuals too much.[26]

Privacy
The Privacy Impact Assessment for EINSTEIN version 2 describes the program in detail.[23]

In the Privacy Impact Assessment (PIA) for EINSTEIN 2 published in 2008, DHS gave a general notice to people who use U.S. federal networks.[23] DHS assumes that Internet users do not expect privacy in the "To" and "From" addresses of their email or in the "IP addresses of the websites they visit" because their service providers use that information for routing. DHS also assumes that people have at least a basic understanding of how computers communicate and know the limits of their privacy rights when they choose to access federal networks.[23] The Privacy Act of 1974 does not apply to EINSTEIN 2 data because its system of records generally does not contain personal information and so is not indexed or queried by the names of individual persons.[23] A PIA for the first version is also available from 2004.[1]

DHS is seeking approval for an EINSTEIN 2 retention schedule in which flow records, alerts, and specific network traffic related to an alert may be maintained for up to three years, and if, for example in the case of a false alert, data is deemed unrelated or potentially collected in error, it can be deleted.[23] According to the DHS privacy assessment for US-CERT's 24x7 Incident Handling and Response Center in 2007, US-CERT data is provided only to those authorized users who "need to know such data for business and security purposes" including security analysts, system administrators and certain DHS contractors. Incident data and contact information are never shared outside of US-CERT and contact information is not analyzed. To secure its data, US-CERT's center began a DHS certification and accreditation process in May 2006 and expected to complete it by the first quarter of fiscal year 2007. As of March 2007, the center had no retention schedule approved by the National Archives and Records Administration and until it does, has no "disposition schedule"—its "records must be considered permanent and nothing may be deleted".[27] As of April 2013, DHS still had no retention schedule but was working "with the NPPD records manager to develop disposition schedules".[28] An update was issued in May 2016.[29]

gollark: JS could be fun because there are so many awful ways to do anything.
gollark: As much as I don't like C, I could do some !!FUN!! stuff.
gollark: Not THAT well, but top quartile apparently.
gollark: Maybe I should play hints about it on osmarks internet radio™ to force people to listen.
gollark: You should believe me when I say things now because I can obviously guess well.

See also

Notes
  1. US-CERT (September 2004). "Privacy Impact Assessment: EINSTEIN Program" (PDF). U.S. Department of Homeland Security, National Cyber Security Division. Retrieved 2008-05-13.
  2. "About US-CERT". U.S. Department of Homeland Security. Archived from the original on 2008-05-25. Retrieved 2008-05-18.
  3. Miller, Jason (May 21, 2007). "Einstein keeps an eye on agency networks". Federal Computer Week. 1105 Media, Inc. Archived from the original on December 19, 2007. Retrieved 2008-05-13.
  4. Lieberman, Joe and Susan Collins (May 2, 2008). "Lieberman and Collins Step Up Scrutiny of Cyber Security Initiative". U.S. Senate Homeland Security and Governmental Affairs Committee. Archived from the original on January 12, 2009. Retrieved 2008-05-14.
  5. "The National Strategy to Secure Cyberspace" (PDF). U.S. government via Department of Homeland Security. February 2003. p. 16. Archived from the original (PDF) on 2008-02-12. Retrieved 2008-05-18.
  6. Bush, George W. (December 17, 2003). "Homeland Security Presidential Directive/Hspd-7" (Press release). Office of the Press Secretary via whitehouse.gov. Retrieved 2008-05-18.
  7. Gail Repsher Emery and Wilson P. Dizard III (September 15, 2003). "Homeland Security unveils new IT security team". Government Computer News. 1105 Media, Inc. Archived from the original on January 23, 2013. Retrieved 2008-05-16.
  8. "About E-GOV: The E-Government Act of 2002". U.S. Office of Management and Budget. Retrieved 2008-05-16.
  9. Johnson, Clay III (November 20, 2007). "Implementation of Trusted Internet Connections (TIC), Memorandum for the Heads of Executive Departments and Agencies (M-08-05)" (PDF). Office of Management and Budget. Retrieved 2010-10-18.
  10. US-CERT (May 19, 2008). "Privacy Impact Assessment for EINSTEIN 2" (PDF). U.S. Department of Homeland Security. p. 4. Retrieved 2008-06-12.
  11. Vijayan, Jaikumar (February 29, 2008). "Q&A: Evans says feds steaming ahead on cybersecurity plan, but with privacy in mind". Computerworld. IDG. Archived from the original on May 2, 2008. Retrieved 2008-05-13.
  12. Office of the Inspector General (June 2007). "Challenges Remain in Securing the Nation's Cyber Infrastructure" (PDF). U.S. Department of Homeland Security. p. 12. Archived from the original (PDF) on 2008-05-15. Retrieved 2008-05-18.
  13. "Fact Sheet: U.S. Department of Homeland Security Five-Year Anniversary Progress and Priorities" (Press release). U.S. Department of Homeland Security. March 6, 2008. Archived from the original on May 14, 2008. Retrieved 2008-05-18.
  14. Apart from 106 listings for "Website" or "Home Page", 486 listings appear in "A-Z Index of U.S. Government Departments and Agencies". U.S. General Services Administration. Retrieved 2008-05-18.
  15. Nakashima, Ellen (January 26, 2008). "Bush Order Expands Network Monitoring: Intelligence Agencies to Track Intrusions". The Washington Post. The Washington Post Company. Retrieved 2008-05-18.
  16. Office of Management and Budget (n.d.). "FY 2001 Report to Congress on Federal Government Information Security Reform" (PDF). Office of Information and Regulatory Affairs. p. 11. Retrieved 2008-05-14.
  17. "Remarks by Homeland Security Secretary Michael Chertoff to the 2008 RSA Conference" (Press release). U.S. Department of Homeland Security. April 8, 2008. Archived from the original on May 14, 2008. Retrieved 2008-05-13.
  18. Vijayan, Jaikumar (February 28, 2008). "Feds downplay privacy fears on plan to expand monitoring of government networks". Computerworld. IDG. Archived from the original on February 16, 2009. Retrieved 2008-05-13.
  19. Mosquera, Mary (July 10, 2008). "OMB: Agencies must shed more gateways". Federal Computer Week. Media, Inc. Archived from the original on July 13, 2008. Retrieved 2008-07-10.
  20. Waterman, Shaun (March 8, 2008). "Analysis: Einstein and U.S. cybersecurity". United Press International. Retrieved 2008-05-13.
  21. "Fact Sheet: Protecting Our Federal Networks Against Cyber Attacks" (Press release). U.S. Department of Homeland Security. April 8, 2008. Archived from the original on May 14, 2008. Retrieved 2008-05-13.
  22. "E P I C A l e r t". 15.11. Electronic Privacy Information Center. May 30, 2008. Retrieved 2008-06-13. Cite journal requires |journal= (help)
  23. US-CERT (May 19, 2008). "Privacy Impact Assessment for EINSTEIN 2" (PDF). U.S. Department of Homeland Security. Retrieved 2008-06-12.
  24. "Homeland Security seeks cyber counterattack system". CNN. Turner Broadcasting System. October 4, 2008. Retrieved 2008-10-07.
  25. Nakashima, Ellen (2009-07-03). "DHS Cybersecurity Plan Will Involve NSA, Telecoms". The Washington Post. Retrieved 2010-05-01.
  26. Radack, Jesselyn (2009-07-14). "NSA's Cyber Overkill: A Project to Safeguard Governmental Computers, Run by the NSA, is too Big a Threat to Americans' Privacy". Los Angeles Times.
  27. "Privacy Impact Assessment for the 24x7 Incident Handling and Response Center" (PDF). U.S. Department of Homeland Security. March 29, 2007. Retrieved 2008-05-14.
  28. "Privacy Impact Assessment for EINSTEIN 3 - Accelerated (E3A)" (PDF). U.S. Department of Homeland Security. April 19, 2013. Retrieved 2013-12-29.
  29. "Privacy Impact Assessment Update for EINSTEIN 3 - Accelerated (E3A)" (PDF). Retrieved 2016-08-17.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.