Is it reportable? Find out in ninety seconds.

Something happened: a trip, a new relationship, an arrest, a strange question from a stranger. Answer a couple of questions and get a straight answer: report or not, who to inform, by when, and with what information. Every answer cites the rule it comes from, listed at the bottom of the page.

Nothing you select here is transmitted or stored. This page has no analytics on your answers and no signup. It runs entirely in your browser.

Who this is for, and the rules it can't see

For: cleared contractor personnel under the NISP with DoD as the cognizant security agency, including anyone in process for eligibility. These are the people DCSA's guidance means by "covered individuals."
Spills and security incidents: if classified information may have been mishandled, disclosed, or compromised, don't use a wizard. Contact your FSO immediately.
SCI or SAP access: your program imposes additional reporting beyond everything here. This tool covers the collateral baseline only; your program security officer's answer wins.
Contract add-ons: if your government customer's contract requires more reporting than the baseline, the contract wins. Ask your FSO.
Uncleared personnel in sensitive positions: you fall under SEAD 3 through your government customer, not the NISP. Contact your customer for guidance.
The universal rule: if anyone, of any nationality, attempts to get unauthorized access to classified information or to exploit your position, report it. Always. No decision tree needed.

First, your access level

This matters: several SEAD 3 requirements apply only at Top Secret or "Q." If you're in process for a clearance, pick the level you're being processed for. If you hold interim eligibility, pick the level of that eligibility.

What happened?

Pick your access level above to begin.

This tool runs entirely in your browser and needs JavaScript enabled to work. That design is deliberate: it is how your answers never leave your device. Enable JavaScript for this page and reload.

A free tool from Bastion, software that does the compliance work FSOs at cleared contractors do by hand, and presents it for approval. If your FSO sent you this link, the reporting part after this answer is exactly the work we automate for them. FSOs: add ?fso=your-security-inbox to this page's link before sharing it, and every report your people send arrives pre-addressed to you.

Question

Answer

The default that never fails: if you're unsure after reading this, tell your FSO anyway and let them make the call. Good faith reporting is not what costs people clearances. Concealment is.

A free tool from Bastion. When you need to make a report, Bastion handles the work for security officers automatically: the intake, the write up, the submission tracking, and the audit ready record.

Sources: Security Executive Agent Directive 3 (SEAD 3), "Reporting Requirements for Personnel with Access to Classified Information or Who Hold a Sensitive Position"; 32 CFR Part 117 (NISPOM rule), § 117.8; DCSA Industrial Security Letter 2021-02 (Aug 12, 2021), Tables 1–4. Guidance reviewed current as of July 2026. This tool is guidance for awareness, not a security determination, legal advice, or a substitute for your company's Standard Practice Procedures. Your FSO and your SPP govern. Nothing entered here is transmitted or stored. Bastion is a product of Apollo Universe, Inc. d/b/a Bastion Software.