The Security Clearances Your Records Still Believed Were Valid

It is 8:03 a.m.

Franck Dubois has barely arrived at Véracier Defense & Security when a message from the Security Department appears in his inbox:

"The DRSD audit has been confirmed for Monday. We need a consolidated status report by the end of today covering Defense security clearances, validity dates, and ongoing renewal procedures."

On paper, the request seems straightforward: identify valid clearances, upcoming expiration dates, and renewals currently in progress.

But in an industrial group like Véracier, the clearances that can actually withstand an audit are not always found in the latest tracking spreadsheet.

• One registry lists a clearance as active.
• An administrative notice mentions a renewal.
• An HR file uses a different identity for the same individual.
• Some documents still refer to legacy classifications such as Confidential Defense, while more recent frameworks use Secret and Top Secret.

Franck opens LightOn and asks the question exactly as he would ask his team:

"Which personnel currently hold a valid Secret or Top Secret clearance, which cases are under renewal, and which expiration dates must be addressed before the DRSD audit?"

The Real Risk Begins Where Reference Systems Meet

Viewed individually, each document appears consistent.

Viewed together, they tell slightly different stories.

• Patrick Vidal appears with a valid clearance in one registry, but under a slightly different identity in an HR file.
• Virginie Marchand, David Owens, and James Hartley appear across multiple systems with consistent statuses.
• Xu Chen, Philippe Courtois, Laure Thibault, and Sophie Marchal all hold active clearances, with expiration dates ranging from 2026 to 2028.

Franck's own case is more complicated:

• An operational registry still lists him as cleared.
• An administrative file highlights a critical upcoming expiration date.
• A renewal notice indicates that a renewal process is already underway.
• An internal tracking table has not yet been updated to reflect the latest status.

Each source captures part of the reality, but none is sufficient on its own.

A few minutes later, the system returns a consolidated view that no individual document ever explicitly provides.

It distinguishes between:

• clearances that are valid and consistent across systems;
• active clearances approaching expiration;
• cases already undergoing renewal;
• identities that must be reconciled across HR, security, and operational records;
• administrative discrepancies that should be documented before the audit;
• supporting evidence linked to every conclusion.

In Franck's case, the answer goes beyond classifying the clearance as simply "valid" or "invalid."

By cross-referencing operational registries, administrative records, and renewal notices, the system confirms that his Secret Defense clearance is currently under renewal and that this status should be explicitly documented as such in the audit report.

Every conclusion is traceable back to the source documents used in the analysis.

By the end of the day, the Security Department has a consolidated report containing:

• cleared personnel;
• classification levels;
• validity dates;
• ongoing renewals;
• administrative discrepancies;
• reconciled identities;
• supporting documentation.

The question is no longer which spreadsheet is correct. The organization now has a consolidated, fully sourced, and defensible view that can withstand scrutiny from the DRSD.

Where Traditional RAG Loses the Thread

The challenge is not finding a clearance in a registry but reconciling multiple reference systems that sometimes contradict one another.

• One registry lists a clearance as active.
• An administrative notice indicates a renewal.
• An HR file uses a different identity for the same individual.
• An operational tracking table has not been updated.
• A historical document still uses an outdated classification label.

A traditional RAG system may retrieve each of these documents. Determining the actual status, however, requires far more than document retrieval.

The system must understand which document is authoritative, reconcile identities, distinguish an active clearance from a renewal process, and explain why a clearance marked as valid in one table may not yet be considered audit-ready.

The risk does not appear in any single document. It emerges when the documents begin to contradict one another.

Why This Use Case Matters

EDiTh's DEF-01 scenario does not test whether a system can retrieve a clearance level from a PDF.

It tests whether a system can reason across administrative statuses, renewal timelines, classification levels, and security reference systems distributed across multiple sources.

The objective is to determine, in a defensible manner, which clearances are genuinely valid at the time of an audit.

For a Security Department, the distinction is critical.

A list extracted from a registry may look sufficient.

A consolidated, fully sourced, and line-by-line explainable assessment is something an auditor can rely on.

Try the Scenario Yourself

DEF-01 is part of EDiTh, LightOn's open-source enterprise benchmark, built around Véracier Industries: a synthetic industrial group composed of 1,004 documents spread across seven subsidiaries, six languages, and multiple administrative, technical, and security reference systems.

Ask the same question:

"Which personnel currently hold a valid Secret or Top Secret clearance, which cases are under renewal, and which expiration dates must be addressed before the DRSD audit?"

Then see whether your system merely retrieves names from registries, or whether it can actually determine which clearances remain valid at audit time.

Start with EDiTh. Then test it against your own documents.

Download the Véracier Industries dataset.

Access LightOn Console and run the scenario yourself.

Want to understand how the corpus was built, how retrieval was performed, and why this answer is so difficult to produce? Read the EDiTh launch article.