Skip to content
← The Issue Encyclopedia

Issue Encyclopedia · Guideline K · Handling Protected Info

Cross-Domain (Spillage) Violation

What the decided record shows for this issue, computed from public DOHA hearing-level decisions. Descriptive history, not a prediction.

Does cross-domain (spillage) violation affect a security clearance?

Cross-Domain (Spillage) Violation is an issue decided under Guideline K, Handling Protected Info. In the decided DOHA record it appears in 29 hearing-level cases, and 34% of the 29 decided ended with access granted (10 granted, 19 denied). The mitigating conditions judges credited most often, and example decisions either way, are below.

Basis: 29 decided hearing-level cases raising this issue. Descriptive history of decided cases, not a prediction.

More questions people ask the record

Decided cases

29

hearing-level decisions raising this issue

Granted

34%

10 granted · 19 denied or revoked

Official mitigating conditions cited

The formal mitigating conditions the case profiles identified on this issue, in cases that were granted and in cases that were denied. Each is shown with its paragraph number and a plain name. Read what each condition says.
  • ¶ 35(a) · So long ago, so infrequent, or so unusual that it is unlikely to recur

    In granted cases
    7
    In denied cases
    0
  • ¶ 35(b) · A favorable response to counseling or remedial security training

    In granted cases
    6
    In denied cases
    0

Recent decided examples

  • The applicant in this case was a 55-year-old senior director for business development at a defense contractor, with a military background as a retired Colonel. The Defense Counterintelligence and Secu…

  • The judge found that the applicant had several past security violations related to handling protected information, but these incidents occurred many years ago and were mitigated by the applicant's pos…

  • The applicant's security clearance was denied due to failure to mitigate security concerns under Guideline E (Personal Conduct) and Guideline K (Handling Protected Information). The applicant admitted…

  • The applicant's security clearance was denied due to failure to mitigate concerns related to personal conduct and handling protected information. The applicant falsified a government questionnaire reg…

See all 29 decisions on this issue

Related issues under Guideline K

How these numbers are measured

Scope: decided hearing-level cases whose per-allegation profile records this issue, matched to the same issue value the search filters use, so a count here and a filtered search always agree. A case raising several issues counts under each one. The mitigating conditions and the credited circumstances below were extracted for a subset of the record, so both are counts of cases rather than rates. Pages exist only for issues with at least 25 decided cases, and † marks any split built on fewer than 20.

Reading the statistics

  • Granted = access granted or continued; Denied = denied or revoked.
  • Grant rate = granted ÷ (granted + denied).
  • † marks figures based on fewer than 20 cases, too few to be reliable.
  • Hovering any rate shows its statistical range (a 95% confidence interval).
  • Figures are descriptive counts over decided, public DOHA ISCR decisions, never predictions or assessments of any pending case.

Where to go from here

Get help with my case

Send us your question, or the Statement of Reasons you received. No charge, and a CASE analyst reads it. Usually five to ten business days.

Ask a question →

I do this for clients

Rank every decision by how closely it matches a matter, see how the assigned judge has ruled, and keep it together with cited exports.

For attorneys and firms →

Decided public cases: descriptive, never a prediction.