<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress.com" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>certification-for-security &amp;laquo; WordPress.com Tag Feed</title>
	<link>http://en.wordpress.com/tag/certification-for-security/</link>
	<description>Feed of posts on WordPress.com tagged "certification-for-security"</description>
	<pubDate>Sun, 19 May 2013 15:20:39 +0000</pubDate>

	<generator>http://en.wordpress.com/tags/</generator>
	<language>en</language>

<item>
<title><![CDATA[Legacy of the Facility Security Officer (FSO)]]></title>
<link>http://industrialsecurity.wordpress.com/2012/06/07/legacy-of-the-facility-security-officer-fso/</link>
<pubDate>Thu, 07 Jun 2012 21:39:00 +0000</pubDate>
<dc:creator>Red Bike Publishing</dc:creator>
<guid>http://industrialsecurity.wordpress.com/2012/06/07/legacy-of-the-facility-security-officer-fso/</guid>
<description><![CDATA[You might already know how to write policy that reflects the NISPOM and export compliance or ITAR re]]></description>
<content:encoded><![CDATA[<div class="MsoPlainText"><span style="font-family:Georgia, serif;font-size:14pt;">You might already know how to write policy that reflects the <a href="http://www.redbikepublishing.com/book/test-book/" target="_blank">NISPOM</a> and export compliance or <a href="http://www.redbikepublishing.com/book/itar/" target="_blank">ITAR</a> regulations. That might very well be an easy task for you. Just like <a href="http://www.redbikepublishing.com/book/isp-certification-manual/" target="_blank">ISP certification</a> mentioned in an earlier post, the policy itself should not be the catch all solution. Just as the certification compliments the bearer’s capabilities, the policy should complement the processes and procedures you have in place.</span></div>
<div class="MsoPlainText"></div>
<div class="MsoPlainText"><span style="font-family:&#34;font-size:14pt;">Policy tells what should happen and is in itself easier to write and have approved than the how to do it found in processes and procedures. Even if you do not know how to write policy, you can always download a boilerplate standard practice procedures, technology control plan, or sample security policies downloaded from Defense Security Services (DSS), or shared by fellow security professional organization contacts. What won’t be so easy to find is policy tailored to your specific needs and how to incorporate them into company business. That will require teamwork with other business unit managers.</span></div>
<div class="MsoPlainText"></div>
<div class="MsoPlainText"><span style="font-family:&#34;font-size:14pt;">Some of the reading audience might understand better than others that most policies exist as “gotchas”. In other words, policies can be used as a basis for discipline. However, unless part of the company DNA, most employees may not know the policy even exists. </span></div>
<div class="MsoPlainText"></div>
<div class="MsoPlainText"><span style="font-family:&#34;font-size:14pt;">For example, suppose you are trying to implement procedures to support your customer’s requirement of approving public release information as identified in the DD Form 254 for <a href="http://www.redbikepublishing.com/book/dod-security-clearance-and-contracts-guidebook/" target="_blank">cleared contractors. </a>You know it’s a requirement, but your company continues to publish contract related information in news releases and on the website without customer approval. To solve this problem, you could:</span></div>
<div class="MsoPlainText"></div>
<div class="MsoPlainText"><span style="font-family:&#34;font-size:14pt;">1. Write a policy and wait for employees to read and comply. If they do not, you can nab them later, pointing out their short falls. </span></div>
<div class="MsoPlainText"></div>
<div class="MsoPlainText"><span style="font-family:&#34;font-size:14pt;">2. Create policy, coordinate with others to create supporting trigger points and courses of action, shop it to all the managers, work together to develop a workflow, and check the progress. </span></div>
<div class="MsoPlainText"></div>
<div class="MsoPlainText"><span style="font-family:&#34;font-size:14pt;">Option two works best because it will be part of an organizational solution and not “just another thing to do.” Option one will cause all kind of trouble and leave the situation unresolved.</span></div>
<div class="MsoPlainText"></div>
<div class="MsoPlainText"><span style="font-family:&#34;font-size:14pt;">An FSO is designated to develop security policy to protect classified information. However, this is not a solution that should be undertaken alone. The entire organization should take part. Just as human resources, facilities, finance and other business units seek the cooperation of the enterprise, the FSO should get similar buy in. With approved and accepted procedures in place, the policy will be easily supported.</span></div>
<div class="MsoPlainText"><span style="font-family:&#34;font-size:14pt;"><br /></span></div>
<div class="MsoPlainText"><span style="font-family:&#34;font-size:14pt;">For more information on establishing security procedures, see&#160;</span><a href="http://www.redbikepublishing.com/book/dod-security-clearance-and-contracts-guidebook/" target="_blank">DoD Security Clearances and Contracts Guidebook</a></div>
<p>Jeffrey W. Bennett, ISP is the owner of Red Bike Publishing <a href="http://www.redbikepublishing.com/" target="_new">Red Bike Publishing </a>.   Jeff is an accomplished writer of non-fiction books, novels and periodicals. He also owns Red bike Publishing. Published books include: &#8220;Get Rich in a Niche-Insider&#8217;s Guide to Self Publishing in a Specialized Industry&#8221; and &#8220;Commitment-A Novel&#8221;.  Jeff is an expert in security and has written many security books including: &#8220;Insider&#8217;s Guide to Security Clearances&#8221; and &#8220;DoD Security Clearances and Contracts Guidebook&#8221;, &#8220;ISP Certification-The Industrial Security Professional Exam Manual&#8221;, and NISPOM/FSO Training&#8221;  See Red Bike Publishing for print copies of: Army Leadership, The Ranger Handbook, The Army Physical Readiness Manual, Drill and Ceremonies, The ITAR,and  The NISPOM
<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5239474422425503931-333205980532256207?l=dodsecurity.blogspot.com' alt='' /></div>
]]></content:encoded>
</item>
<item>
<title><![CDATA[8 Simple Steps FSOs use to Inspect Classified Deliveries]]></title>
<link>http://industrialsecurity.wordpress.com/2012/01/13/8-simple-steps-fsos-use-to-inspect-classified-deliveries/</link>
<pubDate>Fri, 13 Jan 2012 20:43:00 +0000</pubDate>
<dc:creator>Red Bike Publishing</dc:creator>
<guid>http://industrialsecurity.wordpress.com/2012/01/13/8-simple-steps-fsos-use-to-inspect-classified-deliveries/</guid>
<description><![CDATA[The FSO should ensure all arriving classified information is inspected&nbsp;and received into accoun]]></description>
<content:encoded><![CDATA[<div style="text-align:left;"><a href="http://industrialsecurity.files.wordpress.com/2012/01/978-1-936800-80-3hardcopy.jpg" style="clear:left;float:left;margin-bottom:1em;margin-right:1em;"><img border="0" height="240" src="http://industrialsecurity.files.wordpress.com/2012/01/978-1-936800-80-3hardcopy.jpg?w=320&#038;h=240" width="320" /></a></div>
<p>The FSO should ensure all arriving classified information is inspected&#160;and received into accountability. This due diligence is conducted&#160;to ensure that classified information has not been compromised, is&#160;related to a contract, and is properly marked. Regardless of transmission&#160;methods of physical items (mail, courier, overnight, hand carry&#160;and etc.) classified material should be double wrapped. Each layer&#160;serves to protect the classified material from inadvertent and unauthorized&#160;disclosure and should be properly addressed.<br />The classified information should be wrapped and sealed in opaque&#160;material or envelopes.</p>
<p>The NISPOM does not cover seams of wrapped&#160;items, but a good practice is to cover seams with rip-proof opaque tape&#160;or other material that prevents and detects tampering. All seams of the&#160;outer layer should be sealed with opaque tape in an effort to create a solid layer of covering. The item should be wrapped and sealed with the&#160;first layer containing the proper classification level and to and from address&#160;lines. Two copies of receipts should either be attached to the first&#160;layer or inside the first layer. The outer layer should not contain classification&#160;markings and be addressed to a cleared contractor and not a&#160;person’s name.</p>
<p>A good security practice allows for the sender to contact the receiver&#160;that classified material is being sent to their facility. This alerts&#160;the receiver to expect the delivery. Many times program managers, engineers<br />or other technical employees are anticipating the delivery, but&#160;may not have all the details of delivery times and dates. However an&#160;FSO to FSO coordination can provide all the information of the transaction<br />in advance.</p>
<p>Regardless of transmission methods, the recipient should examine&#160;the outer wrapping for evidence of tampering or to otherwise to&#160;inspect that there has been no compromise of classified material. Classified<br />material should be double wrapped or in other words have two&#160;independent layers of protection. Each layer consists of opaque material&#160;such as: an envelope, paper, box or other strong wrapping material.</p>
<p>1. &#160;The first part of the inspection should be conducted to look for&#160;evidence of tearing, ripping, re-wrapping or some other means of unauthorized&#160;access to the material.</p>
<p>2. &#160;Next, the shipping label should be reviewed for full approved classified&#160;mailing address, return address.</p>
<p>3. &#160;There should be no classification&#160;markings on the outer layer of the item; the outer layer should not draw&#160;attention to the classified material inside. Classification markings on&#160;the outside of a package are a security violation.</p>
<p>4. &#160;The inner layer should be inspected the same way as the outer layer&#160;for evidence of tampering or unauthorized disclosure.</p>
<p>5. &#160;However, the inside wrapping should contain the full address of the recipient&#160;as well as classification markings on the top, bottom, front and&#160;back. TOP SECRET and SECRET material should have a&#160;packing list or receipt of contents either on the outside or inside of the&#160;container.</p>
<p>6. &#160;If a receipt is included, the receiver should sign it&#160;and return it to the sender.&#160;Receipts are not necessary with the shipment of CONFIDENTIAL&#160;material.</p>
<p>7. &#160;The receiver should then check the receipt against the contents to&#160;ensure the item has been identified correctly and all items are accounted&#160;for. The properly filled out receipt should list the sender, the addressee&#160;and correctly identify the contents by an unclassified title and&#160;appropriate quantity. Since the receipt may be filed for administrative&#160;and compliance purposes, the inspector should ensure it contains no&#160;classified information. If the receipt contains a classified title, the sender&#160;may be able to coordinate for an unclassified title for internal use.</p>
<p>8. &#160;Once all the checks and verification&#160;are complete, the receiver can then sign a copy of the receipt and&#160;return to the sender, thus closing the loop on the sender’s accounting&#160;responsibilities.</p>
<p>
<div style="text-align:center;"><b>Items to inspect when receiving classified deliveries:</b></div>
<p>
<ul>
<li>Outside wrapper:</li>
<ul>
<li>&#160;Evidence of tamper</li>
<li>Seams sealed with anti-rip tape</li>
<li>Label is addressed to organization (not individual)</li>
</ul>
<li>Inside wrapper:</li>
<ul>
<li>Evidence of tamper</li>
<li>Seams sealed with anti-rip tape&#160;</li>
<li>Inside label addressed to recipient&#160;</li>
<li>Inside wrapper is marked with appropriate classification&#160;</li>
<li>Receipts / packing list included for SECRET and above&#160;</li>
<li>Compare receipt/packing list against contents&#160;</li>
<li>Ensure items are classified properly&#160;</li>
<li>Sign receipts and return to sender</li>
</ul>
</ul>
<div style="text-align:justify;"><b>Figure 5-3 </b>(From <a href="http://www.redbikepublishing.com/book/dod-security-clearance-and-contracts-guidebook/" target="_blank">DoD Security Clearances and Contracts Guidebook</a>) The FSO should ensure that all classified deliveries are inspected&#160;prior to bringing them into accountability. Such checks are necessary to &#160;ensure items were sent properly, were not tampered with in transit, contain&#160;correct items and are authorized for storage in the classified holdings</div>
<p>
<div style="text-align:justify;"></div>
<p>Learn more FSO required skills in&#160;<a href="http://www.redbikepublishing.com/book/dod-security-clearance-and-contracts-guidebook/" target="_blank">DoD Security Clearances and Contracts Guidebook</a></p>
<p>Jeffrey W. Bennett, ISP is the owner of Red Bike Publishing <a href="http://www.redbikepublishing.com/" target="_new">Red Bike Publishing </a>.   Jeff is an accomplished writer of non-fiction books, novels and periodicals. He also owns Red bike Publishing. Published books include: &#8220;Get Rich in a Niche-Insider&#8217;s Guide to Self Publishing in a Specialized Industry&#8221; and &#8220;Commitment-A Novel&#8221;.  Jeff is an expert in security and has written many security books including: &#8220;Insider&#8217;s Guide to Security Clearances&#8221; and &#8220;DoD Security Clearances and Contracts Guidebook&#8221;, &#8220;ISP Certification-The Industrial Security Professional Exam Manual&#8221;, and NISPOM/FSO Training&#8221;  See Red Bike Publishing for print copies of: Army Leadership, The Ranger Handbook, The Army Physical Readiness Manual, Drill and Ceremonies, The ITAR,and  The NISPOM
<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5239474422425503931-1327093757569252830?l=dodsecurity.blogspot.com' alt='' /></div>
]]></content:encoded>
</item>

</channel>
</rss>
