TSA IT access controls audit · OIG-26-40
Department of Homeland Security Office of Inspector General · tsa-it-access-controls-oig-26-40-2026
- Recorded status
- Final report issued September 30, 2026; five recommendations listed open on Oversight.gov
- Last verified
- Listed organization
- Transportation Security Administration
- Organization location
- United States
- Source data refreshed
- Report number
- OIG-26-40
- Report date
- September 30, 2026
- Recommendations listed open
- 5
- Questioned costs
- $0
- Publicly described control themes
- Privileged access, service-account approval, periodic access review and timely account removal
What this record covers
DHS OIG report OIG-26-40 reviews TSA information-technology access controls. The public report page identifies issues involving privileged-account permissions, approval of service accounts, annual access reviews, and timely removal of former employees’ access; it lists five open recommendations. The detailed report is Sensitive Security Information, and the public page has redacted or incomplete numeric details. This record therefore does not infer sample sizes or percentages. The audit concerns control implementation, not a certification award or proof that an account was exploited.
How to verify it for your work
Revalidate privileged and service accounts against job need
System owner, identity and access management lead, privileged-access manager and ISSO · At onboarding or role change, during each required access review and before audit sampling
Export the in-scope privileged and service-account population from authoritative identity systems. For each account, preserve a named business owner, purpose, approving authority, system scope, assigned privileges, authentication method, last-use evidence and review date. Compare entitlements with approved role requirements. Remove or reduce access through a logged change, and test the effective permissions after the change. Store Sensitive Security Information only in approved handling systems and follow agency marking and distribution rules.
Evidence to keep A dated population, approval trail, reviewer decisions, access-change tickets and post-change permission checks under the correct information-handling controls.
Make separation events remove access on time
Human resources operations, identity operations, contracting officer representative and system owners · At termination or contract end, with recurring reconciliation of HR and identity records
Define the authoritative event that starts the removal clock, the systems and tokens included, the accountable queue and escalation path. Reconcile separation and contract-end records to disabled accounts, including cloud identities, privileged credentials, shared credentials and physical or application access where relevant. Measure completion against the applicable policy deadline; investigate late, missing and reactivated accounts; and test samples from event to final disabled state.
Evidence to keep A dated event-to-disable report, documented exceptions, revocation logs, escalation records and a reviewer-tested sample from source event through effective access removal.