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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

286<br />

Bureau of Investigation and others. These personnel supported the notion that supervisors<br />

report more often than coworkers, but neither set of people reports much. They offered a<br />

series of reasons why this should be so, and made some recommendations to improve the<br />

situation. Security managers suggested the following reasons why people may not report:<br />

Cultural resistance.<br />

Negative perceptions of reporting and its consequences (to the reporter and to<br />

the person reported).<br />

Lack of knowledge and experience of security officers, supervisors, and the<br />

workforce with reporting requirements.<br />

Unclear relationships between security, employee assistance programs, and<br />

other functions in the organization.<br />

Focus Groups<br />

Supervisors and coworkers in focus groups supported the managers’ estimates on<br />

the frequency of supervisor and coworker reports. They noted their own reluctance to<br />

report on their colleagues. Reasons for not reporting included:<br />

Cannot see the nexus between certain reportable behaviors and national<br />

security.<br />

Fear they will cause people problems.<br />

Fear that reported colleagues will be harmed because the system may not be<br />

fair to them.<br />

Fear that they will lose control once the report has been made to Security.<br />

Fear of negative repercussions to themselves for reporting.<br />

However, they are not resistant to reporting serious infractions. It is simply that<br />

the DoD Directive 5200.2-R reporting requirements are perceived as being too broad and<br />

amorphous and, thus, very difficult to implement. The regulation requires that supervisors<br />

be trained in recognizing “indicators that may signal matters of personnel security<br />

concern” and that supervisors and coworkers report “information with potentially serious<br />

security significance.” While these phrases may have been clear to the original framers of<br />

the directive, they are far from obvious to personnel in the field. Noted a supervisor, “We<br />

need clearer rules about what should be reported up the chain.” However, even in the<br />

absence of such guidance, supervisors and coworkers do intuitively distinguish between<br />

behaviors that are directly related to national security (which they say they have no<br />

problem reporting) and behaviors that are associated with reliability and suitability for<br />

employment (which they are hesitant to report).<br />

The single most important reason employees gave for seldom reporting is that<br />

they personally cannot see the precise connection—the nexus—between certain<br />

behaviors and national security. They said that they do not know where to draw the line<br />

between egregious security-related behaviors and gray-area suitability or personal<br />

behaviors—the kinds of problems that, while important, are seen as less critical in terms<br />

of security risk management and are not directly linked in people’s minds with the<br />

compromise of security or with espionage.<br />

If the connection were made apparent, they said they would be more motivated to<br />

report in order to protect their country and national security. In response to this concern,<br />

PERSEREC subsequently developed a brochure that lists behaviors that always should be<br />

reported if they become known. Reporting these behaviors requires no judgment calls.<br />

The brochure is called Counterintelligence Reporting Essentials (CORE): A Practical<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!