• Log In
  • Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • HomePage
  • About
  • Structure
  • Schedule
    • First Half of the Semester
      • Week 1: Overview of Course
      • Week 2: TCP/IP and Network Architecture
      • Week 3: Reconnaissance
      • Week 4: Vulnerability scanning
      • Week 5: System and User enumeration
      • Week 6: Sniffers
      • Week 7: NetCat, Hellcat
    • Second Half of the Semester
      • Week 8: Social Engineering, Encoding, and Encryption
      • Week 9: Malware
      • Week 10: Web application hacking, Intercepting Proxies, and URL Editing
      • Week 11: SQL injection
      • Week 12: Web Services
      • Week 13: Evasion Techniques
      • Week 14: Review of all topics and wrap up discussion
  • Assignments
    • Analysis Reports
    • Quizzes & Tests
  • Webex
  • Harvard Coursepack
  • Gradebook

ITACS 5211: Introduction to Ethical Hacking

Wade Mackay

The OPM breach report: A long time coming

October 18, 2016 by Shain R. Amzovski 3 Comments

This article discusses the breach of OPM (Federal Office of Personal Management), this breach leaked information about roughly 22 million current and former employees became public in mid-2015.  It took close to another 15 months for Congress to complete a report on it. Hackers, said to be from China, were inside the OPM system starting in 2012, but were not detected until March 20, 2014.  A second group, who worked as a third-party contractor was also able to get access to OPM’s system, and it was not discovered until May 2015.  I was employed with the federal government in May 2014, so there was a chance that my information was apart of this 22 million names that were sent out.  I received several e-mails and letters in the mail informing me about the breach.  Below is a list of what the inspector general found about the security in place at OPM.

An inspector general’s report from November 2014 was blunt about a lack of basic security measures including:

  • A lack of encryption
  • No two-factor authentication for workers remotely accessing the system
  • No inventory of servers and databases
  • Lack of awareness of all the systems connected to its networks

Article Link:

http://www.csoonline.com/article/3130682/data-breach/the-opm-breach-report-a-long-time-coming.html?google_editors_picks=true

Filed Under: Week 08: Social Engineering, Encoding and Encryption Tagged With:

Reader Interactions

Comments

  1. Ahmed A. Alkaysi says

    October 18, 2016 at 3:13 pm

    This is why it is extremely important to have some sort of security control measures in place. Even the most basic will include requirements for 2 factor authentication or knowing what systems are connected to the networks. It always seems like Government entities have the worse security measures in place.

    Log in to Reply
  2. Vaibhav Shukla says

    October 19, 2016 at 10:27 am

    I think its a very bad approach by a government agency in maintaining its IT infrastructure.
    The IT systems were like full of vulnerabilities and the officials were waiting for such data breach event to take place in-order to put everything on track .
    The common items mentioned in it are like some of the key in maintaining IT security in an organization and even small business now a days are protecting themselves from these factors

    Log in to Reply
  3. Jason A Lindsley says

    October 19, 2016 at 6:41 pm

    It took them 15 months to create the report on this. I wonder how long it will take them to remediate all the security findings. The other day a colleague was talking about how the OPM breach was much more than government employee information. I can see now how the SF-86 form could also provide personal and confidential information of employee’s family members. The SF-86 also contains contains information on financial history, investments, arrest records, medical problems, any drug or alcohol problems and other material that could be used to blackmail an employee.

    The thing that bothers me most in this case is the lack of accountability. Any publicly held organization would have required much stronger action against the leadership team.

    Log in to Reply

Leave a Reply Cancel reply

You must be logged in to post a comment.

Primary Sidebar

Weekly Discussions

  • Uncategorized (133)
  • Week 01: Overview (1)
  • Week 02: TCP/IP and Network Architecture (8)
  • Week 03: Reconnaisance (25)
  • Week 04: Vulnerability Scanning (19)
  • Week 05: System and User Enumeration (15)
  • Week 06: Sniffers (9)
  • Week 07: NetCat and HellCat (11)
  • Week 08: Social Engineering, Encoding and Encryption (12)
  • Week 09: Malware (14)
  • Week 10: Web Application Hacking (12)
  • Week 11: SQL Injection (11)
  • Week 12: Web Services (10)
  • Week 13: Evasion Techniques (7)
  • Week 14: Review of all topics (5)

Copyright © 2025 · Magazine Pro Theme on Genesis Framework · WordPress · Log in