OPM merges security investigation databases


The Office of Personnel Management is streamlining a database with records on feds and contractors with access to security clearance investigative records, with the apparent goal of putting an additional layer of security over the actual contents of government background investigations.

The federal government is in the midst of an overhaul of the security clearance process, the result of reviews initiated in the wake of last year's deadly Navy Yard shooting, perpetrated by a cleared federal contractor with a record of mental health issues and violent behavior that did not show up in his security check.

A report to President Barack Obama released in February advised switching to an automated continuous evaluation method for updating clearances, rather than periodic reinvestigations, and using a risk-based approach to identify subjects for more intensive probes. The report also advised a coordinated, government-wide approach to managing the IT around clearance investigations and adjudications.

An OPM spokesperson told FCW that the planned changes put forth in a Feb. 27 Federal Register Notice were administrative in nature, and did not represent new policy. However, the planned changes mesh closely with the administration's goal of creating a collaborative, enterprise-wide, case-management tool for investigations. OPM plans to merge several internal databases – the Security Officer Control Files and the Adjudication Officer Control Files – with data on individuals with access to OPM facilities or systems, including OPM employees, contractors, and others who need access to OPM systems.

Notably, OPM plans to exclude records on employees and contractors working for outside agencies who were themselves the subject of investigations by OPM at the request of outside federal agencies. This would appear to constitute the meat of the OPM internal database – the case files containing information on suitability and security investigations conducted by OPM on behalf of federal agencies. The notice advises further that owing to these changes, "requests for background investigations maintained in the Adjudications Officer Control Files will be denied," presumably because they no longer reside in that system.

The changes to the records system was announced in the Federal Register as required by the Privacy Act of 1974.

It's not clear from the Federal Register notice how the investigation case files will be housed, or in whose custody. An OPM spokesperson did not shed light on the content of the notice in a brief conversation. However, isolating the investigative case files from OPM's internal employee and contractor files make sense in the context of building an interoperable system that can support the analytics necessary to conduct the kind of ongoing automated evaluations sought by the administration. However, there has been no public announcement of the creation of the kind of enterprise-wide case management system envisioned under the report to the president, so it's not clear whether the notice is part of a larger plan to prep clearance investigations records for an overhaul, or simple IT housekeeping.

OPM has also come under fire in recent months because its main investigative contractor, United States Investigative Services, is being sued for fraud over employee claims that it fast-tracked clearances without conducting the required investigations. The Justice Department joined the whistleblower suit, which is proceeding in the Washington, D.C., federal district court. USIS has until June 4 to respond to the charges. As a result of the controversy, OPM has put its own employees in charge of reviewing background checks before they are sent to the requesting agencies for adjudication.

OPM is also adding security checks to the merged system of records it is retaining. Employees will require a completed investigation or a grant of interim access before gaining access to the records contained in the unified database. Records themselves are to be stored as digital images on a secure, local network or in locked metal cabinets in a secure facility.

About the Author

Adam Mazmanian is executive editor of FCW.

Before joining the editing team, Mazmanian was an FCW staff writer covering Congress, government-wide technology policy and the Department of Veterans Affairs. Prior to joining FCW, Mazmanian was technology correspondent for National Journal and served in a variety of editorial roles at B2B news service SmartBrief. Mazmanian has contributed reviews and articles to the Washington Post, the Washington City Paper, Newsday, New York Press, Architect Magazine and other publications.

Click here for previous articles by Mazmanian. Connect with him on Twitter at @thisismaz.


  • 2018 Fed 100

    The 2018 Federal 100

    This year's Fed 100 winners show just how much committed and talented individuals can accomplish in federal IT. Read their profiles to learn more!

  • Census
    How tech can save money for 2020 census

    Trump campaign taps census question as a fund-raising tool

    A fundraising email for the Trump-Pence reelection campaign is trying to get supporters behind a controversial change to the census -- asking respondents whether or not they are U.S. citizens.

  • Cloud
    DOD cloud

    DOD's latest cloud moves leave plenty of questions

    Speculation is still swirling about the implications of the draft solicitation for JEDI -- and about why a separate agreement for cloud-migration services was scaled back so dramatically.

Stay Connected

FCW Update

Sign up for our newsletter.

I agree to this site's Privacy Policy.