Skip to content
← The Issue Encyclopedia

Issue Encyclopedia · Guideline K · Handling Protected Info

Improperly Compiled or Used Protected Info

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

Does improperly compiled or used protected info affect a security clearance?

Improperly Compiled or Used Protected Info is an issue decided under Guideline K, Handling Protected Info. In the decided DOHA record it appears in 26 hearing-level cases, and 38% of the 26 decided ended with access granted (10 granted, 16 denied). The mitigating conditions judges credited most often, and example decisions either way, are below.

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

More questions people ask the record

Decided cases

26

hearing-level decisions raising this issue

Granted

38%

10 granted · 16 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
    2
  • ¶ 35(b) · A favorable response to counseling or remedial security training

    In granted cases
    5
    In denied cases
    2
  • ¶ 35(c) · The violations followed inadequate training or unclear instructions

    In granted cases
    3
    In denied cases
    2

Recent decided examples

  • The applicant in this case was a 64-year-old principal process engineer employed by a defense contractor since 1979. He applied for a security clearance in 2017, but the Defense Counterintelligence an…

  • The applicant in this case was a 53-year-old employee of a defense contractor who sought a security clearance after being found culpable for two significant security violations under Guideline K, whic…

  • The applicant's security clearance was denied due to failure to mitigate security concerns under multiple guidelines. The allegations included mishandling classified equipment, providing false informa…

  • Applicant, a retired Navy E-8 and current defense contractor employee, was denied a clearance after the judge found unresolved concerns under Guidelines K, M, E, J, and G. The decision rested on repea…

See all 26 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.