Summary
A software engineer and former Navy member was denied a security clearance under Guideline E (Personal Conduct) due to multiple incidents of misconduct. The applicant had previously held a clearance, but the appeal board determined that subsequent security-significant conduct precluded reciprocity.
Key disqualifying conditions included the applicant's false representation of professional credentials and a non-judicial punishment for assault. Additionally, the applicant was terminated from employment for cause, a fact not disclosed in previous clearance adjudications.
While mitigating conditions E2.A5.2.1, E2.A5.2.2, and E2.A5.2.3 were considered, they were insufficient to overcome the concerns raised by the applicant's actions. The denial was ultimately upheld, emphasizing that the applicant's post-clearance conduct, including providing false information and an undisclosed termination, demonstrated a pattern of behavior inconsistent with security requirements.
Conditions Referenced
- E2.A5.1.2raisedPersonal Conduct
- E2.A5.2.1rejectedThe Behavior Was Not RecentThe applicant's misconduct occurred after his previous clearance was granted.
- E2.A5.2.2rejectedThe Individual Did Not Commit the OffenseThe applicant admitted to the misconduct during cross-examination.
- E2.A5.2.3rejectedThe Individual Has Taken Positive Steps to Reduce or Eliminate VulnerabilityThe applicant's claims of good character were insufficient to mitigate the security concerns.
Key Rule Quoted
“The general standard is that a clearance may be granted only when ‘clearly consistent with the interests of the national security.’”
Procedural Posture
- SOR issuedOct 29, 2009
- Answer filed—
- Hearing heldApr 27, 2010
- Decision dateJul 19, 2010
Cite For
- Denial of Security Clearance Due to Personal Conduct Under Guideline E
- Reciprocity Not Granted Due to Subsequent Misconduct
- Insufficient Mitigation of Security Concerns Despite Prior Clearance History