09.12.2012 Views

2003 IMTA Proceedings - International Military Testing Association

2003 IMTA Proceedings - International Military Testing Association

2003 IMTA Proceedings - International Military Testing Association

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Strategies for Increased Reporting of Security-Relevant Behavior*<br />

Kent S. Crawford<br />

Defense Personnel Security Research Center<br />

Suzanne Wood<br />

Consultant to Northrop Grumman Mission Systems<br />

Introduction<br />

United States federal policies and those of the Department of Defense (DoD) are<br />

designed to ensure that the cleared workforce is reliable, trustworthy, and loyal. One of<br />

the requirements of such policies is that supervisors and coworkers who work in<br />

classified environments report to security managers any behavior they observe among<br />

workplace colleagues that may be of security concern. In essence, supervisors and<br />

coworkers, working closely with each other as they do, can observe or become aware of<br />

behaviors that might suggest a risk to national security.<br />

These policy requirements are in place as one means to prevent Americans from<br />

committing espionage. However, espionage is a rare event. One is not likely ever to<br />

encounter a spy, much less observe an act of espionage. So while catching spies may be<br />

an ultimate goal for these policies and the reason to report counterintelligence- (CI) and<br />

security-related behavior, the policies are also designed to regularly evaluate the millions<br />

of ordinary people in the workplace who have access to classified information, people<br />

who have no intention of committing espionage but are likely—over a period of time or<br />

in changing contexts—to develop personal problems that may possibly question their<br />

reliability and trustworthiness. The philosophy behind policies nowadays is that the<br />

government is not just trying to root out spies: by asking employees to report, the<br />

government is not only identifying potential security risks but actually helping employees<br />

take care of the kinds of human problems that plague us all from time to time. However,<br />

reporting policy—based on the adjudicative guidelines—has mixed together the kinds of<br />

behavior that should always be reported. CI- and security-related behaviors are mixed<br />

with reliability and suitability problems. This has led to confusion among supervisors and<br />

coworkers about what behaviors are the most important to report. It is this confusion that<br />

often paralyses employees: if they are not sure exactly what to report, they simply report<br />

nothing.<br />

Evidence gathered during a recent PERSEREC study (Wood & Marshall-Mies,<br />

<strong>2003</strong>) shows that the reporting rate is in fact very low. Supervisors and coworkers are<br />

reluctant to inform security managers about many behaviors that they observe in the<br />

workplace because they believe them to be too personal to report. It is ironic that the very<br />

behaviors that the government wants people to report—in order to be able to help them—<br />

are the very ones that supervisors and coworkers are loath to share with authorities.<br />

Employees are, however, more willing to report behaviors that are egregious and appear<br />

to have a more direct some connection with national security.<br />

_______________________________________________________________________<br />

*The views expressed in this paper are those of the authors and do not necessarily reflect<br />

those of the United States Department of Defense.<br />

283<br />

45 th Annual Conference of the <strong>International</strong> <strong>Military</strong> <strong>Testing</strong> <strong>Association</strong><br />

Pensacola, Florida, 3-6 November <strong>2003</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!