<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://sandbox.capmembers.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=BReady72</id>
	<title>CAPipedia Sandbox - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://sandbox.capmembers.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=BReady72"/>
	<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/wiki/Special:Contributions/BReady72"/>
	<updated>2026-04-22T07:44:46Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.45.1</generator>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=259</id>
		<title>For Official Use Only</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=259"/>
		<updated>2018-08-14T22:58:28Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== For Official Use Only (FOUO) ==&lt;br /&gt;
For Official Use Only (FOUO) is a document designation, not a classification. This designation is used by Department of Defense and a number of other federal agencies to identify information or material which, although unclassified, may not be appropriate for public release.&lt;br /&gt;
&lt;br /&gt;
=== Classification Definitions ===&lt;br /&gt;
These definitions are quoted from DoD Directive 5200-1. Refer to the DoD Directive if information on higher classifications if needed.&lt;br /&gt;
 &lt;br /&gt;
Unclassified controlled information shall be applied to information that requires protection for types of information that require application of controls and protective measures for a variety of reasons. Type of information that fall within this category include &amp;quot;For Official Use Only&amp;quot; information, &amp;quot;Sensitive But Unclassified&amp;quot; (formerly &amp;quot;Limited Official Use&amp;quot;) information, “Law Enforcement Sensitive”, &amp;quot;Sensitive Information&amp;quot; as defined in the Computer Security Act of 1987, and information contained in technical documents. &lt;br /&gt;
 &lt;br /&gt;
=== Communications Security (COMSEC) ===&lt;br /&gt;
The protection resulting from all measures designed to deny unauthorized persons information of value that might be derived from the possession and study of telecommunications and to ensure the authenticity of such communications. COMSEC includes cryptosecurity, emission security, transmission security, and physical security of COMSEC material and information. i.e. – CAP radio frequencies&lt;br /&gt;
 &lt;br /&gt;
=== Information Security ===&lt;br /&gt;
The system of policies, procedures, and requirements established under the authority of E.O. 12958 to protect information that, if subjected to unauthorized disclosure, could reasonably be expected to cause damage to the national security.&lt;br /&gt;
 &lt;br /&gt;
=== Access ===&lt;br /&gt;
The ability and opportunity to obtain knowledge of classified information, unclassified sensitive information, LE Sensitive, DEA Sensitive, etc.   The proper clearance and/or background investigation granted by DoD, Law Enforcement Agency, CAP, etc will be needed for access. Agencies may require CAP members to sign a binding non-disclosure agreement before granting members access.&lt;br /&gt;
 &lt;br /&gt;
=== Need to know ===&lt;br /&gt;
CAP members who have been authorized by a customer/tasking agency, posses the proper access level, and designated CAP authority will be granted access to unclassified or classified mission information. The customer may restrict CAP personnel who have a need to know. Member’s involvement in a particular mission will determine need to know. i.e. – IC working a sensitive mission. Mission information will not be shared with personnel that do not have a “need to know”.&lt;br /&gt;
 &lt;br /&gt;
=== Close Hold/Sensitive ===&lt;br /&gt;
Mission information that is unclassified but must be safeguarded. Loss of Close Hold or Sensitive information would compromise ongoing operations for a supported agency. Members will safeguard Close Hold/Sensitive unclassified information to prevent deliberate or accidental disclosure.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Classified missions will receive their designation from the request/tasking agency and not designated or derived by CAP. CAP may designate an unclassified mission as Sensitive but Unclassified or Close Hold. Requesting agencies may designate a mission Law Enforcement Sensitive, DEA Sensitive, or Sensitive Information.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=258</id>
		<title>For Official Use Only</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=258"/>
		<updated>2018-08-14T22:58:13Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== For Official Use Only (FOUO) ==&lt;br /&gt;
For Official Use Only (FOUO) is a document designation, not a classification. This designation is used by Department of Defense and a number of other federal agencies to identify information or material which, although unclassified, may not be appropriate for public release.&lt;br /&gt;
&lt;br /&gt;
=== Classification Definitions ===&lt;br /&gt;
These definitions are quoted from DoD Directive 5200-1. Refer to the DoD Directive if information on higher classifications if needed.&lt;br /&gt;
 &lt;br /&gt;
Unclassified controlled information shall be applied to information that requires protection for types of information that require application of controls and protective measures for a variety of reasons. Type of information that fall within this category include &amp;quot;For Official Use Only&amp;quot; information, &amp;quot;Sensitive But Unclassified&amp;quot; (formerly &amp;quot;Limited Official Use&amp;quot;) information, “Law Enforcement Sensitive”, &amp;quot;Sensitive Information&amp;quot; as defined in the Computer Security Act of 1987, and information contained in technical documents. &lt;br /&gt;
 &lt;br /&gt;
=== Communications Security (COMSEC) ===&lt;br /&gt;
The protection resulting from all measures designed to deny unauthorized persons information of value that might be derived from the possession and study of telecommunications and to ensure the authenticity of such communications. COMSEC includes cryptosecurity, emission security, transmission security, and physical security of COMSEC material and information. i.e. – CAP radio frequencies&lt;br /&gt;
 &lt;br /&gt;
=== Information Security ===&lt;br /&gt;
The system of policies, procedures, and requirements established under the authority of E.O. 12958 to protect information that, if subjected to unauthorized disclosure, could reasonably be expected to cause damage to the national security.&lt;br /&gt;
 &lt;br /&gt;
=== Access ===&lt;br /&gt;
The ability and opportunity to obtain knowledge of classified information, unclassified sensitive information, LE Sensitive, DEA Sensitive, etc.   The proper clearance and/or background investigation granted by DoD, Law Enforcement Agency, CAP, etc will be needed for access. Agencies may require CAP members to sign a binding non-disclosure agreement before granting members access.&lt;br /&gt;
 &lt;br /&gt;
=== Need to know ===&lt;br /&gt;
CAP members who have been authorized by a customer/tasking agency, posses the proper access level, and designated CAP authority will be granted access to unclassified or classified mission information. The customer may restrict CAP personnel who have a need to know. Member’s involvement in a particular mission will determine need to know. i.e. – IC working a sensitive mission. Mission information will not be shared with personnel that do not have a “need to know”.&lt;br /&gt;
 &lt;br /&gt;
=== Close Hold/Sensitive ===&lt;br /&gt;
Mission information that is unclassified but must be safeguarded. Loss of Close Hold or Sensitive information would compromise ongoing operations for a supported agency. Members will safeguard Close Hold/Sensitive unclassified information to prevent deliberate or accidental disclosure.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Classified missions will receive their designation from the request/tasking agency and not designated or derived by CAP. CAP may designate an unclassified mission as Sensitive but Unclassified or Close Hold. Requesting agencies may designate a mission Law Enforcement Sensitive, DEA Sensitive, or Sensitive Information.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=257</id>
		<title>For Official Use Only</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=257"/>
		<updated>2018-08-14T22:57:28Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== For Official Use Only (FOUO) ==&lt;br /&gt;
For Official Use Only (FOUO) is a document designation, not a classification. This designation is used by Department of Defense and a number of other federal agencies to identify information or material which, although unclassified, may not be appropriate for public release.&lt;br /&gt;
&lt;br /&gt;
=== Classification Definitions ===&lt;br /&gt;
These definitions are quoted from DoD Directive 5200-1. Refer to the DoD Directive if information on higher classifications if needed.&lt;br /&gt;
 &lt;br /&gt;
Unclassified controlled information shall be applied to information that requires protection for types of information that require application of controls and protective measures for a variety of reasons. Type of information that fall within this category include &amp;quot;For Official Use Only&amp;quot; information, &amp;quot;Sensitive But Unclassified&amp;quot; (formerly &amp;quot;Limited Official Use&amp;quot;) information, “Law Enforcement Sensitive”, &amp;quot;Sensitive Information&amp;quot; as defined in the Computer Security Act of 1987, and information contained in technical documents. &lt;br /&gt;
 &lt;br /&gt;
=== Communications Security (COMSEC) ===&lt;br /&gt;
The protection resulting from all measures designed to deny unauthorized persons information of value that might be derived from the possession and study of telecommunications and to ensure the authenticity of such communications. COMSEC includes cryptosecurity, emission security, transmission security, and physical security of COMSEC material and information. i.e. – CAP radio frequencies&lt;br /&gt;
 &lt;br /&gt;
=== Information Security ===&lt;br /&gt;
The system of policies, procedures, and requirements established under the authority of E.O. 12958 to protect information that, if subjected to unauthorized disclosure, could reasonably be expected to cause damage to the national security.&lt;br /&gt;
 &lt;br /&gt;
=== Access ===&lt;br /&gt;
The ability and opportunity to obtain knowledge of classified information, unclassified sensitive information, LE Sensitive, DEA Sensitive, etc.   The proper clearance and/or background investigation granted by DoD, Law Enforcement Agency, CAP, etc will be needed for access. Agencies may require CAP members to sign a binding non-disclosure agreement before granting members access.&lt;br /&gt;
 &lt;br /&gt;
=== Need to know ===&lt;br /&gt;
CAP members who have been authorized by a customer/tasking agency, posses the proper access level, and designated CAP authority will be granted access to unclassified or classified mission information. The customer may restrict CAP personnel who have a need to know. Member’s involvement in a particular mission will determine need to know. i.e. – IC working a sensitive mission. Mission information will not be shared with personnel that do not have a “need to know”.&lt;br /&gt;
 &lt;br /&gt;
=== Close Hold/Sensitive ===&lt;br /&gt;
Mission information that is unclassified but must be safeguarded. Loss of Close Hold or Sensitive information would compromise ongoing operations for a supported agency. Members will safeguard Close Hold/Sensitive unclassified information to prevent deliberate or accidental disclosure.&lt;br /&gt;
 &lt;br /&gt;
Classified missions will receive their designation from the request/tasking agency and not designated or derived by CAP. CAP may designate an unclassified mission as Sensitive but Unclassified or Close Hold. Requesting agencies may designate a mission Law Enforcement Sensitive, DEA Sensitive, or Sensitive Information.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=256</id>
		<title>For Official Use Only</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=256"/>
		<updated>2018-08-14T22:53:52Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== For Official Use Only (FOUO) ==&lt;br /&gt;
=== For Official Use Only (FOUO) is a document designation, not a classification. This designation is used by Department of Defense and a number of other federal agencies to identify information or material which, although unclassified, may not be appropriate for public release. ===&lt;br /&gt;
&lt;br /&gt;
=== Classification Definitions ===&lt;br /&gt;
These definitions are quoted from DoD Directive 5200-1. Refer to the DoD Directive if information on higher classifications if needed.&lt;br /&gt;
 &lt;br /&gt;
Unclassified controlled information shall be applied to information that requires protection for types of information that require application of controls and protective measures for a variety of reasons. Type of information that fall within this category include &amp;quot;For Official Use Only&amp;quot; information, &amp;quot;Sensitive But Unclassified&amp;quot; (formerly &amp;quot;Limited Official Use&amp;quot;) information, “Law Enforcement Sensitive”, &amp;quot;Sensitive Information&amp;quot; as defined in the Computer Security Act of 1987, and information contained in technical documents. &lt;br /&gt;
 &lt;br /&gt;
=== Communications Security (COMSEC) ===&lt;br /&gt;
The protection resulting from all measures designed to deny unauthorized persons information of value that might be derived from the possession and study of telecommunications and to ensure the authenticity of such communications. COMSEC includes cryptosecurity, emission security, transmission security, and physical security of COMSEC material and information. i.e. – CAP radio frequencies&lt;br /&gt;
 &lt;br /&gt;
=== Information Security ===&lt;br /&gt;
The system of policies, procedures, and requirements established under the authority of E.O. 12958 to protect information that, if subjected to unauthorized disclosure, could reasonably be expected to cause damage to the national security.&lt;br /&gt;
 &lt;br /&gt;
=== Access ===&lt;br /&gt;
The ability and opportunity to obtain knowledge of classified information, unclassified sensitive information, LE Sensitive, DEA Sensitive, etc.   The proper clearance and/or background investigation granted by DoD, Law Enforcement Agency, CAP, etc will be needed for access. Agencies may require CAP members to sign a binding non-disclosure agreement before granting members access.&lt;br /&gt;
 &lt;br /&gt;
=== Need to know ===&lt;br /&gt;
CAP members who have been authorized by a customer/tasking agency, posses the proper access level, and designated CAP authority will be granted access to unclassified or classified mission information. The customer may restrict CAP personnel who have a need to know. Member’s involvement in a particular mission will determine need to know. i.e. – IC working a sensitive mission. Mission information will not be shared with personnel that do not have a “need to know”.&lt;br /&gt;
 &lt;br /&gt;
=== Close Hold/Sensitive ===&lt;br /&gt;
Mission information that is unclassified but must be safeguarded. Loss of Close Hold or Sensitive information would compromise ongoing operations for a supported agency. Members will safeguard Close Hold/Sensitive unclassified information to prevent deliberate or accidental disclosure.&lt;br /&gt;
 &lt;br /&gt;
Classified missions will receive their designation from the request/tasking agency and not designated or derived by CAP. CAP may designate an unclassified mission as Sensitive but Unclassified or Close Hold. Requesting agencies may designate a mission Law Enforcement Sensitive, DEA Sensitive, or Sensitive Information.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=255</id>
		<title>For Official Use Only</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=255"/>
		<updated>2018-08-14T22:51:49Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== For Official Use Only (FOUO) ==&lt;br /&gt;
For Official Use Only (FOUO) is a document designation, not a classification. This designation is used by Department of Defense and a number of other federal agencies to identify information or material which, although unclassified, may not be appropriate for public release.&lt;br /&gt;
&lt;br /&gt;
Classification Definitions&lt;br /&gt;
These definitions are quoted from DoD Directive 5200-1. Refer to the DoD Directive if information on higher classifications if needed.&lt;br /&gt;
 &lt;br /&gt;
Unclassified controlled information shall be applied to information that requires protection for types of information that require application of controls and protective measures for a variety of reasons. Type of information that fall within this category include &amp;quot;For Official Use Only&amp;quot; information, &amp;quot;Sensitive But Unclassified&amp;quot; (formerly &amp;quot;Limited Official Use&amp;quot;) information, “Law Enforcement Sensitive”, &amp;quot;DEA Sensitive Information&amp;quot;, &amp;quot;Sensitive Information&amp;quot; as defined in the Computer Security Act of 1987, and information contained in technical documents. &lt;br /&gt;
 &lt;br /&gt;
Communications Security (COMSEC). The protection resulting from all measures designed to deny unauthorized persons information of value that might be derived from the possession and study of telecommunications and to ensure the authenticity of such communications. COMSEC includes cryptosecurity, emission security, transmission security, and physical security of COMSEC material and information. i.e. – CAP radio frequencies&lt;br /&gt;
 &lt;br /&gt;
Information Security. The system of policies, procedures, and requirements established under the authority of E.O. 12958 to protect information that, if subjected to unauthorized disclosure, could reasonably be expected to cause damage to the national security.&lt;br /&gt;
 &lt;br /&gt;
Access. The ability and opportunity to obtain knowledge of classified information, unclassified sensitive information, LE Sensitive, DEA Sensitive, etc.   The proper clearance and/or background investigation granted by DoD, Law Enforcement Agency, CAP, etc will be needed for access. Agencies may require CAP members to sign a binding non-disclosure agreement before granting members access.&lt;br /&gt;
 &lt;br /&gt;
Need to know – CAP members who have been authorized by a customer/tasking agency, posses the proper access level, and designated CAP authority will be granted access to unclassified or classified mission information. The customer may restrict CAP personnel who have a need to know. Member’s involvement in a particular mission will determine need to know. i.e. – IC working a sensitive mission. Mission information will not be shared with personnel that do not have a “need to know”.&lt;br /&gt;
 &lt;br /&gt;
Close Hold/Sensitive – Mission information that is unclassified but must be safeguarded. Loss of Close Hold or Sensitive information would compromise ongoing operations for a supported agency. Members will safeguard Close Hold/Sensitive unclassified information to prevent deliberate or accidental disclosure.&lt;br /&gt;
 &lt;br /&gt;
Classified missions will receive their designation from the request/tasking agency and not designated or derived by CAP. CAP may designate an unclassified mission as Sensitive but Unclassified or Close Hold. Requesting agencies may designate a mission Law Enforcement Sensitive, DEA Sensitive, or Sensitive Information.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=254</id>
		<title>Personally Identifiable Information</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=254"/>
		<updated>2018-08-14T22:49:06Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Personally Identifiable Information (PII) ==&lt;br /&gt;
&lt;br /&gt;
== [https://www.gocivilairpatrol.com/media/cms/R001_002_15BAF8B12FA4B.pdf CAP Regulation 1-2] ==&lt;br /&gt;
&lt;br /&gt;
This regulation defines rules for protecting Personally Identifiable Information (PII), collected, generated, or maintained by Civil Air Patrol (CAP), from unauthorized disclosure and emphasizes the role of CAP users in ensuring that the appropriate physical and technical safeguards are in place to protect all CAP systems (both hard copy and electronic) that contain PII. This regulation applies to all CAP members.&lt;br /&gt;
&lt;br /&gt;
=== 1. General ===&lt;br /&gt;
Personally identifiable information (PII) is CAP confidential information about an individual that can be used to distinguish or trace that individual’s identity. Examples of PII include, but are not limited to, social security number; age; marital status; race; date and place of birth; telephone numbers; other demographic, medical history, personal, medical and financial information. Unauthorized access to the PII of members/employees must be prevented to the maximum extent possible. PII shall only be made available to those individuals who have a specific need to have such information and shall be provided for official CAP business only.&lt;br /&gt;
&lt;br /&gt;
=== 2. Responsibilities ===&lt;br /&gt;
==== a. Commanders/Directors ====&lt;br /&gt;
# Only require the collection of personal information that is absolutely necessary to conduct CAP business (see paragraph 3a below).&lt;br /&gt;
# Ensure that all personnel within their area of responsibility understand the need to protect PII.&lt;br /&gt;
==== b. Members ====&lt;br /&gt;
Protect PII that has come into their possession during the normal conduct of CAP business IAW paragraph 3b below.&lt;br /&gt;
&lt;br /&gt;
=== 3. Protection ===&lt;br /&gt;
==== a. Limit the use of PII to absolute need. Whenever possible, forms, applications and other documents should use only the individual’s name, CAP grade and CAPID. Additional information about the individual may then be drawn from the online personnel database, which has appropriate security measures. ====&lt;br /&gt;
==== b. Limit access to PII that has been acquired as part of normal CAP processes. Personal discipline on the part of the custodian of CAP records/documents containing PII is key to preventing unauthorized access. ====&lt;br /&gt;
# CAP records/documents containing PII must be kept under lock and key or in a secure electronic file that is password protected when the records/documents are not in use.&lt;br /&gt;
# When leaving your work area, records containing PII must not be left open and unattended, or in any manner that would allow the data to be seen by an unauthorized individual.&lt;br /&gt;
# Do not leave unattended any laptops, tablet PCs, smartphones, USB flash drives or personal digital assistants (PDA) containing PII.&lt;br /&gt;
# Delete any data containing PII as soon as practical after completing the tasking for which the PII data was acquired.&lt;br /&gt;
# CAP publications and forms issued by any level of command that include requirements to collect or use PII must contain instructions for protecting PII.&lt;br /&gt;
# All devices containing PII should be password-enabled or have data encryption standards installed (if possible) to prevent unauthorized access to the data if the device is stolen or lost.&lt;br /&gt;
# If PII is to be transmitted via radio, only the absolute minimum amount of information essential to mission accomplishment should be transmitted using encrypted radio transmissions if possible.&lt;br /&gt;
&lt;br /&gt;
=== 3. Disposal === &lt;br /&gt;
==== Disposal methods are considered adequate if the personal data is rendered unrecognizable or beyond reconstruction.&lt;br /&gt;
==== a. Examples of disposal methods for paper records include, but are not limited to tearing, burning, shredding, or mutilation. ====&lt;br /&gt;
==== b. Examples of disposal methods for electronic records and media include, but are not limited to, overwriting, degaussing, disintegration, pulverization, burning, shredding or sanding. Just deleting electronic files containing PII is not sufficient. ====&lt;br /&gt;
&lt;br /&gt;
=== 5. What to do in the case of a Breach. ===&lt;br /&gt;
==== If a CAP member becomes aware that his/her or another member’s PII may have been released, that member will notify his/her commander as soon as feasible. The commander is responsible for ensuring that the member(s) whose information may have been released or disclosed is notified of that release of information, to include the specific PII that may have been released. If a single incident results in the release or disclosure of PII of 10 or more members, the commander will notify the National Headquarters General Counsel’s office (NHQ/GC) of the name and CAPID of the member(s) whose information may have been released, with an information copy of the notification to the group, wing and region commander (as appropriate). Individual wings need to consult with their legal officers to assure compliance with state standards, if any. ====&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=253</id>
		<title>Personally Identifiable Information</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=253"/>
		<updated>2018-08-14T22:48:00Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Personally Identifiable Information (PII) ==&lt;br /&gt;
&lt;br /&gt;
== [https://www.gocivilairpatrol.com/media/cms/R001_002_15BAF8B12FA4B.pdf CAP Regulation 1-2] ==&lt;br /&gt;
&lt;br /&gt;
This regulation defines rules for protecting Personally Identifiable Information (PII), collected, generated, or maintained by Civil Air Patrol (CAP), from unauthorized disclosure and emphasizes the role of CAP users in ensuring that the appropriate physical and technical safeguards are in place to protect all CAP systems (both hard copy and electronic) that contain PII. This regulation applies to all CAP members.&lt;br /&gt;
&lt;br /&gt;
=== 1. General ===&lt;br /&gt;
Personally identifiable information (PII) is CAP confidential information about an individual that can be used to distinguish or trace that individual’s identity. Examples of PII include, but are not limited to, social security number; age; marital status; race; date and place of birth; telephone numbers; other demographic, medical history, personal, medical and financial information. Unauthorized access to the PII of members/employees must be prevented to the maximum extent possible. PII shall only be made available to those individuals who have a specific need to have such information and shall be provided for official CAP business only.&lt;br /&gt;
&lt;br /&gt;
=== 2. Responsibilities ===&lt;br /&gt;
==== a. Commanders/Directors ====&lt;br /&gt;
# Only require the collection of personal information that is absolutely necessary to conduct CAP business (see paragraph 3a below).&lt;br /&gt;
# Ensure that all personnel within their area of responsibility understand the need to protect PII.&lt;br /&gt;
==== b. Members ====&lt;br /&gt;
# Protect PII that has come into their possession during the normal conduct of CAP business IAW paragraph 3b below.&lt;br /&gt;
&lt;br /&gt;
=== 3. Protection ===&lt;br /&gt;
==== a. Limit the use of PII to absolute need. Whenever possible, forms, applications and other documents should use only the individual’s name, CAP grade and CAPID. Additional information about the individual may then be drawn from the online personnel database, which has appropriate security measures. ====&lt;br /&gt;
==== b. Limit access to PII that has been acquired as part of normal CAP processes. Personal discipline on the part of the custodian of CAP records/documents containing PII is key to preventing unauthorized access. ====&lt;br /&gt;
# CAP records/documents containing PII must be kept under lock and key or in a secure electronic file that is password protected when the records/documents are not in use.&lt;br /&gt;
# When leaving your work area, records containing PII must not be left open and unattended, or in any manner that would allow the data to be seen by an unauthorized individual.&lt;br /&gt;
# Do not leave unattended any laptops, tablet PCs, smartphones, USB flash drives or personal digital assistants (PDA) containing PII.&lt;br /&gt;
# Delete any data containing PII as soon as practical after completing the tasking for which the PII data was acquired.&lt;br /&gt;
# CAP publications and forms issued by any level of command that include requirements to collect or use PII must contain instructions for protecting PII.&lt;br /&gt;
# All devices containing PII should be password-enabled or have data encryption standards installed (if possible) to prevent unauthorized access to the data if the device is stolen or lost.&lt;br /&gt;
# If PII is to be transmitted via radio, only the absolute minimum amount of information essential to mission accomplishment should be transmitted using encrypted radio transmissions if possible.&lt;br /&gt;
&lt;br /&gt;
=== 3. Disposal === &lt;br /&gt;
==== Disposal methods are considered adequate if the personal data is rendered unrecognizable or beyond reconstruction.&lt;br /&gt;
==== a. Examples of disposal methods for paper records include, but are not limited to tearing, burning, shredding, or mutilation. ====&lt;br /&gt;
==== b. Examples of disposal methods for electronic records and media include, but are not limited to, overwriting, degaussing, disintegration, pulverization, burning, shredding or sanding. Just deleting electronic files containing PII is not sufficient. ====&lt;br /&gt;
&lt;br /&gt;
=== 5. What to do in the case of a Breach. ===&lt;br /&gt;
==== If a CAP member becomes aware that his/her or another member’s PII may have been released, that member will notify his/her commander as soon as feasible. The commander is responsible for ensuring that the member(s) whose information may have been released or disclosed is notified of that release of information, to include the specific PII that may have been released. If a single incident results in the release or disclosure of PII of 10 or more members, the commander will notify the National Headquarters General Counsel’s office (NHQ/GC) of the name and CAPID of the member(s) whose information may have been released, with an information copy of the notification to the group, wing and region commander (as appropriate). Individual wings need to consult with their legal officers to assure compliance with state standards, if any. ====&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=252</id>
		<title>Personally Identifiable Information</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=252"/>
		<updated>2018-08-14T22:47:09Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Personally Identifiable Information (PII) ==&lt;br /&gt;
&lt;br /&gt;
== [https://www.gocivilairpatrol.com/media/cms/R001_002_15BAF8B12FA4B.pdf CAP Regulation 1-2] ==&lt;br /&gt;
&lt;br /&gt;
This regulation defines rules for protecting Personally Identifiable Information (PII), collected, generated, or maintained by Civil Air Patrol (CAP), from unauthorized disclosure and emphasizes the role of CAP users in ensuring that the appropriate physical and technical safeguards are in place to protect all CAP systems (both hard copy and electronic) that contain PII. This regulation applies to all CAP members.&lt;br /&gt;
&lt;br /&gt;
=== 1. General ===&lt;br /&gt;
Personally identifiable information (PII) is CAP confidential information about an individual that can be used to distinguish or trace that individual’s identity. Examples of PII include, but are not limited to, social security number; age; marital status; race; date and place of birth; telephone numbers; other demographic, medical history, personal, medical and financial information. Unauthorized access to the PII of members/employees must be prevented to the maximum extent possible. PII shall only be made available to those individuals who have a specific need to have such information and shall be provided for official CAP business only.&lt;br /&gt;
&lt;br /&gt;
=== 2. Responsibilities ===&lt;br /&gt;
==== a. Commanders/Directors ====&lt;br /&gt;
# Only require the collection of personal information that is absolutely necessary to conduct CAP business (see paragraph 3a below).&lt;br /&gt;
# Ensure that all personnel within their area of responsibility understand the need to protect PII.&lt;br /&gt;
==== b. Members ====&lt;br /&gt;
# Protect PII that has come into their possession during the normal conduct of CAP business IAW paragraph 3b below.&lt;br /&gt;
&lt;br /&gt;
=== 3. Protection ===&lt;br /&gt;
==== a. Limit the use of PII to absolute need. Whenever possible, forms, applications and other documents should use only the individual’s name, CAP grade and CAPID. Additional information about the individual may then be drawn from the online personnel database, which has appropriate security measures. ====&lt;br /&gt;
==== b. Limit access to PII that has been acquired as part of normal CAP processes. Personal discipline on the part of the custodian of CAP records/documents containing PII is key to preventing unauthorized access. ====&lt;br /&gt;
# CAP records/documents containing PII must be kept under lock and key or in a secure electronic file that is password protected when the records/documents are not in use.&lt;br /&gt;
# When leaving your work area, records containing PII must not be left open and unattended, or in any manner that would allow the data to be seen by an unauthorized individual.&lt;br /&gt;
# Do not leave unattended any laptops, tablet PCs, smartphones, USB flash drives or personal digital assistants (PDA) containing PII.&lt;br /&gt;
# Delete any data containing PII as soon as practical after completing the tasking for which the PII data was acquired.&lt;br /&gt;
# CAP publications and forms issued by any level of command that include requirements to collect or use PII must contain instructions for protecting PII.&lt;br /&gt;
# All devices containing PII should be password-enabled or have data encryption standards installed (if possible) to prevent unauthorized access to the data if the device is stolen or lost.&lt;br /&gt;
# If PII is to be transmitted via radio, only the absolute minimum amount of information essential to mission accomplishment should be transmitted using encrypted radio transmissions if possible.&lt;br /&gt;
&lt;br /&gt;
=== 3. Disposal === &lt;br /&gt;
==== a. Disposal methods are considered adequate if the personal data is rendered unrecognizable or beyond reconstruction.&lt;br /&gt;
==== a. Examples of disposal methods for paper records include, but are not limited to tearing, burning, shredding, or mutilation. ====&lt;br /&gt;
==== b. Examples of disposal methods for electronic records and media include, but are not limited to, overwriting, degaussing, disintegration, pulverization, burning, shredding or sanding. Just deleting electronic files containing PII is not sufficient. ====&lt;br /&gt;
&lt;br /&gt;
=== 5. What to do in the case of a Breach. ===&lt;br /&gt;
If a CAP member becomes aware that his/her or another member’s PII may have been released, that member will notify his/her commander as soon as feasible. The commander is responsible for ensuring that the member(s) whose information may have been released or disclosed is notified of that release of information, to include the specific PII that may have been released. If a single incident results in the release or disclosure of PII of 10 or more members, the commander will notify the National Headquarters General Counsel’s office (NHQ/GC) of the name and CAPID of the member(s) whose information may have been released, with an information copy of the notification to the group, wing and region commander (as appropriate). Individual wings need to consult with their legal officers to assure compliance with state standards, if any.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=251</id>
		<title>Personally Identifiable Information</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=251"/>
		<updated>2018-08-14T22:45:55Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Personally Identifiable Information (PII) ==&lt;br /&gt;
&lt;br /&gt;
== [https://www.gocivilairpatrol.com/media/cms/R001_002_15BAF8B12FA4B.pdf CAP Regulation 1-2] ==&lt;br /&gt;
&lt;br /&gt;
This regulation defines rules for protecting Personally Identifiable Information (PII), collected, generated, or maintained by Civil Air Patrol (CAP), from unauthorized disclosure and emphasizes the role of CAP users in ensuring that the appropriate physical and technical safeguards are in place to protect all CAP systems (both hard copy and electronic) that contain PII. This regulation applies to all CAP members.&lt;br /&gt;
&lt;br /&gt;
=== 1. General ===&lt;br /&gt;
Personally identifiable information (PII) is CAP confidential information about an individual that can be used to distinguish or trace that individual’s identity. Examples of PII include, but are not limited to, social security number; age; marital status; race; date and place of birth; telephone numbers; other demographic, medical history, personal, medical and financial information. Unauthorized access to the PII of members/employees must be prevented to the maximum extent possible. PII shall only be made available to those individuals who have a specific need to have such information and shall be provided for official CAP business only.&lt;br /&gt;
&lt;br /&gt;
=== 2. Responsibilities ===&lt;br /&gt;
==== a. Commanders/Directors ====&lt;br /&gt;
# Only require the collection of personal information that is absolutely necessary to conduct CAP business (see paragraph 3a below).&lt;br /&gt;
# Ensure that all personnel within their area of responsibility understand the need to protect PII.&lt;br /&gt;
==== b. Members ====&lt;br /&gt;
# Protect PII that has come into their possession during the normal conduct of CAP business IAW paragraph 3b below.&lt;br /&gt;
&lt;br /&gt;
=== 3. Protection ===&lt;br /&gt;
==== a. Limit the use of PII to absolute need. Whenever possible, forms, applications and other documents should use only the individual’s name, CAP grade and CAPID. Additional information about the individual may then be drawn from the online personnel database, which has appropriate security measures. ====&lt;br /&gt;
==== b. Limit access to PII that has been acquired as part of normal CAP processes. Personal discipline on the part of the custodian of CAP records/documents containing PII is key to preventing unauthorized access. ====&lt;br /&gt;
# CAP records/documents containing PII must be kept under lock and key or in a secure electronic file that is password protected when the records/documents are not in use.&lt;br /&gt;
# When leaving your work area, records containing PII must not be left open and unattended, or in any manner that would allow the data to be seen by an unauthorized individual.&lt;br /&gt;
# Do not leave unattended any laptops, tablet PCs, smartphones, USB flash drives or personal digital assistants (PDA) containing PII.&lt;br /&gt;
# Delete any data containing PII as soon as practical after completing the tasking for which the PII data was acquired.&lt;br /&gt;
# CAP publications and forms issued by any level of command that include requirements to collect or use PII must contain instructions for protecting PII.&lt;br /&gt;
# All devices containing PII should be password-enabled or have data encryption standards installed (if possible) to prevent unauthorized access to the data if the device is stolen or lost.&lt;br /&gt;
# If PII is to be transmitted via radio, only the absolute minimum amount of information essential to mission accomplishment should be transmitted using encrypted radio transmissions if possible.&lt;br /&gt;
&lt;br /&gt;
=== 3. Disposal === &lt;br /&gt;
==== a. Disposal methods are considered adequate if the personal data is rendered unrecognizable or beyond reconstruction.&lt;br /&gt;
==== a. Examples of disposal methods for paper records include, but are not limited to tearing, burning, shredding, or mutilation. ====&lt;br /&gt;
==== b. Examples of disposal methods for electronic records and media include, but are not limited to, overwriting, degaussing, disintegration, pulverization, burning, shredding or sanding. Just deleting electronic files containing PII is not sufficient. ====&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=250</id>
		<title>Personally Identifiable Information</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=250"/>
		<updated>2018-08-14T22:40:49Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Personally Identifiable Information (PII) ==&lt;br /&gt;
&lt;br /&gt;
== [https://www.gocivilairpatrol.com/media/cms/R001_002_15BAF8B12FA4B.pdf CAP Regulation 1-2] ==&lt;br /&gt;
&lt;br /&gt;
This regulation defines rules for protecting Personally Identifiable Information (PII), collected, generated, or maintained by Civil Air Patrol (CAP), from unauthorized disclosure and emphasizes the role of CAP users in ensuring that the appropriate physical and technical safeguards are in place to protect all CAP systems (both hard copy and electronic) that contain PII. This regulation applies to all CAP members.&lt;br /&gt;
&lt;br /&gt;
=== General ===&lt;br /&gt;
Personally identifiable information (PII) is CAP confidential information about an individual that can be used to distinguish or trace that individual’s identity. Examples of PII include, but are not limited to, social security number; age; marital status; race; date and place of birth; telephone numbers; other demographic, medical history, personal, medical and financial information. Unauthorized access to the PII of members/employees must be prevented to the maximum extent possible. PII shall only be made available to those individuals who have a specific need to have such information and shall be provided for official CAP business only.&lt;br /&gt;
&lt;br /&gt;
=== Responsibilities ===&lt;br /&gt;
==== a. Commanders/Directors ====&lt;br /&gt;
# Only require the collection of personal information that is absolutely necessary to conduct CAP business (see paragraph 3a below).&lt;br /&gt;
# Ensure that all personnel within their area of responsibility understand the need to protect PII.&lt;br /&gt;
==== b. Members ====&lt;br /&gt;
# Protect PII that has come into their possession during the normal conduct of CAP business IAW paragraph 3b below.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=249</id>
		<title>Personally Identifiable Information</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=249"/>
		<updated>2018-08-14T22:39:43Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Personally Identifiable Information (PII) ==&lt;br /&gt;
&lt;br /&gt;
== [https://www.gocivilairpatrol.com/media/cms/R001_002_15BAF8B12FA4B.pdf CAP Regulation 1-2] ==&lt;br /&gt;
&lt;br /&gt;
This regulation defines rules for protecting Personally Identifiable Information (PII), collected, generated, or maintained by Civil Air Patrol (CAP), from unauthorized disclosure and emphasizes the role of CAP users in ensuring that the appropriate physical and technical safeguards are in place to protect all CAP systems (both hard copy and electronic) that contain PII. This regulation applies to all CAP members.&lt;br /&gt;
&lt;br /&gt;
=== General ===&lt;br /&gt;
Personally identifiable information (PII) is CAP confidential information about an individual that can be used to distinguish or trace that individual’s identity. Examples of PII include, but are not limited to, social security number; age; marital status; race; date and place of birth; telephone numbers; other demographic, medical history, personal, medical and financial information. Unauthorized access to the PII of members/employees must be prevented to the maximum extent possible. PII shall only be made available to those individuals who have a specific need to have such information and shall be provided for official CAP business only.&lt;br /&gt;
&lt;br /&gt;
=== Responsibilities ===&lt;br /&gt;
==== Commanders/Directors ====&lt;br /&gt;
# Only require the collection of personal information that is absolutely necessary to conduct CAP business (see paragraph 3a below).&lt;br /&gt;
# Ensure that all personnel within their area of responsibility understand the need to protect PII.&lt;br /&gt;
==== Members ====&lt;br /&gt;
# Protect PII that has come into their possession during the normal conduct of CAP business IAW paragraph 3b below.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=248</id>
		<title>Personally Identifiable Information</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=248"/>
		<updated>2018-08-14T22:37:03Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Personally Identifiable Information (PII) ==&lt;br /&gt;
&lt;br /&gt;
== [https://www.gocivilairpatrol.com/media/cms/R001_002_15BAF8B12FA4B.pdf CAP Regulation 1-2] ==&lt;br /&gt;
&lt;br /&gt;
This regulation defines rules for protecting Personally Identifiable Information (PII), collected, generated, or maintained by Civil Air Patrol (CAP), from unauthorized disclosure and emphasizes the role of CAP users in ensuring that the appropriate physical and technical safeguards are in place to protect all CAP systems (both hard copy and electronic) that contain PII. This regulation applies to all CAP members.&lt;br /&gt;
&lt;br /&gt;
=== General ===&lt;br /&gt;
Personally identifiable information (PII) is CAP confidential information about an individual that can be used to distinguish or trace that individual’s identity. Examples of PII include, but are not limited to, social security number; age; marital status; race; date and place of birth; telephone numbers; other demographic, medical history, personal, medical and financial information. Unauthorized access to the PII of members/employees must be prevented to the maximum extent possible. PII shall only be made available to those individuals who have a specific need to have such information and shall be provided for official CAP business only.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=247</id>
		<title>Personally Identifiable Information</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=247"/>
		<updated>2018-08-14T22:36:15Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Personally Identifiable Information (PII) ==&lt;br /&gt;
&lt;br /&gt;
== CAP Regulation 1-2 ==&lt;br /&gt;
&lt;br /&gt;
This regulation defines rules for protecting Personally Identifiable Information (PII), collected, generated, or maintained by Civil Air Patrol (CAP), from unauthorized disclosure and emphasizes the role of CAP users in ensuring that the appropriate physical and technical safeguards are in place to protect all CAP systems (both hard copy and electronic) that contain PII. This regulation applies to all CAP members.&lt;br /&gt;
&lt;br /&gt;
=== General ===&lt;br /&gt;
Personally identifiable information (PII) is CAP confidential information about an individual that can be used to distinguish or trace that individual’s identity. Examples of PII include, but are not limited to, social security number; age; marital status; race; date and place of birth; telephone numbers; other demographic, medical history, personal, medical and financial information. Unauthorized access to the PII of members/employees must be prevented to the maximum extent possible. PII shall only be made available to those individuals who have a specific need to have such information and shall be provided for official CAP business only.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=246</id>
		<title>Personally Identifiable Information</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=246"/>
		<updated>2018-08-14T22:36:00Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Personally Identifiable Information (PII) ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
== CAP Regulation 1-2 ==&lt;br /&gt;
&lt;br /&gt;
This regulation defines rules for protecting Personally Identifiable Information (PII), collected, generated, or maintained by Civil Air Patrol (CAP), from unauthorized disclosure and emphasizes the role of CAP users in ensuring that the appropriate physical and technical safeguards are in place to protect all CAP systems (both hard copy and electronic) that contain PII. This regulation applies to all CAP members.&lt;br /&gt;
&lt;br /&gt;
=== General ===&lt;br /&gt;
Personally identifiable information (PII) is CAP confidential information about an individual that can be used to distinguish or trace that individual’s identity. Examples of PII include, but are not limited to, social security number; age; marital status; race; date and place of birth; telephone numbers; other demographic, medical history, personal, medical and financial information. Unauthorized access to the PII of members/employees must be prevented to the maximum extent possible. PII shall only be made available to those individuals who have a specific need to have such information and shall be provided for official CAP business only.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=245</id>
		<title>Personally Identifiable Information</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=245"/>
		<updated>2018-08-14T22:30:40Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Personally identifiable information (PII) ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Personally identifiable information (PII) is any data that could potentially identify a specific individual. Any information that can be used to distinguish one person from another and can be used for de-anonymizing anonymous data can be considered PII.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=244</id>
		<title>Personally Identifiable Information</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Personally_Identifiable_Information&amp;diff=244"/>
		<updated>2018-08-14T22:30:23Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== Personally identifiable information (PII) ==&amp;lt;br&amp;gt;  Personally identifiable information (PII) is any data that could potentially identify a specific individual. Any informati...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Personally identifiable information (PII) ==&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Personally identifiable information (PII) is any data that could potentially identify a specific individual. Any information that can be used to distinguish one person from another and can be used for de-anonymizing anonymous data can be considered PII.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=243</id>
		<title>For Official Use Only</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=243"/>
		<updated>2018-08-14T22:29:11Z</updated>

		<summary type="html">&lt;p&gt;BReady72: /* For Official Use Only */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== For Official Use Only (FOUO) ==&lt;br /&gt;
For Official Use Only (FOUO) is a document designation, not a classification. This designation is used by Department of Defense and a number of other federal agencies to identify information or material which, although unclassified, may not be appropriate for public release.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=242</id>
		<title>For Official Use Only</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=For_Official_Use_Only&amp;diff=242"/>
		<updated>2018-08-14T22:28:53Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== For Official Use Only == For Official Use Only (FOUO) is a document designation, not a classification. This designation is used by Department of Defense and a number of oth...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== For Official Use Only ==&lt;br /&gt;
For Official Use Only (FOUO) is a document designation, not a classification. This designation is used by Department of Defense and a number of other federal agencies to identify information or material which, although unclassified, may not be appropriate for public release.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Computer_Disposal&amp;diff=217</id>
		<title>Computer Disposal</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Computer_Disposal&amp;diff=217"/>
		<updated>2018-08-09T01:50:42Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Procedure for disposal of a CAP issued computer ==&lt;br /&gt;
Disposal of CAP property is addressed in CAPR 174-1. The regulation implements policies created by the Civil Air Patrol Senior Advisory Group (CSAG) and requirements contained in Congressional legislation, DoD Directive 3210.6R, DoD Grants and Agreements Regulations (DoDGARs), DoD Manual 4160.21-M, Defense Materiel Disposition Manual, and the Cooperative Agreement between Civil Air Patrol (CAP) and the United States Air Force. It establishes CAP’s standards of property management for obtaining, controlling and disposing of all forms of CAP property. The policies presented here are necessary to ensure the availability of resources for missions and assure CAP’s compliance with directives. Guidance for proper utilization and protection of CAP property is also included. Policies contained in this regulation are directive and apply to all volunteers and units including National Staff and employees, regions, wings, groups, squadrons and flights.&lt;br /&gt;
&lt;br /&gt;
Paragraph 2-28 covers Retiring Property. Non-expendable items may only be removed from a CAP’s property inventory by following the retirement process in ORMS. The property’s source determines which approvals (wing, region, NHQ, CAP-USAF, etc.) are required for retirement.&lt;br /&gt;
&lt;br /&gt;
Per NHQ/LG, CAP issued laptops having the current ORMS value less than $500 may be disposed of locally at the discretion and approval of the Wing or Region Commander. The hard drives must be either removed and destroyed or wiped using DoD level technology. Programs similar to ones found at [https://dban.org/ DBAN.org]. CAP recommends a five (5) level wipe process. This will take some time and as much as a day to accomplish, plan accordingly. Once the drive has been removed or wiped the computer may be disposed of locally, preferably recycled. Obtain a receipt from the facility and forward to NHQ/LG for documentation in ORMS.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Computer_Disposal&amp;diff=216</id>
		<title>Computer Disposal</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Computer_Disposal&amp;diff=216"/>
		<updated>2018-08-09T01:28:55Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Procedure for disposal of a CAP issued computer ==&lt;br /&gt;
Disposal of CAP property is addressed in CAPR 174-1. The regulation implements policies created by the Civil Air Patrol Senior Advisory Group (CSAG) and requirements contained in Congressional legislation, DoD Directive 3210.6R, DoD Grants and Agreements Regulations (DoDGARs), DoD Manual 4160.21-M, Defense Materiel Disposition Manual, and the Cooperative Agreement between Civil Air Patrol (CAP) and the United States Air Force. It establishes CAP’s standards of property management for obtaining, controlling and disposing of all forms of CAP property. The policies presented here are necessary to ensure the availability of resources for missions and assure CAP’s compliance with directives. Guidance for proper utilization and protection of CAP property is also included. Policies contained in this regulation are directive and apply to all volunteers and units including National Staff and employees, regions, wings, groups, squadrons and flights.&lt;br /&gt;
&lt;br /&gt;
Paragraph 2-28 covers Retiring Property. Non-expendable items may only be removed from a CAP’s property inventory by following the retirement process in ORMS. The property’s source determines which approvals (wing, region, NHQ, CAP-USAF, etc.) are required for retirement.&lt;br /&gt;
&lt;br /&gt;
Per NHQ/LG, CAP issued laptops having the current ORMS value less than $500 may be disposed of locally at the discretion and approval of the Wing or Region Commander.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Computer_Disposal&amp;diff=212</id>
		<title>Computer Disposal</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Computer_Disposal&amp;diff=212"/>
		<updated>2018-08-09T01:18:41Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Procedure for disposal of a CAP issued computer ==&lt;br /&gt;
Disposal of CAP property is addressed in CAPR 174-1. The regulation implements policies created by the Civil Air Patrol Senior Advisory Group (CSAG) and requirements contained in Congressional legislation, DoD Directive 3210.6R, DoD Grants and Agreements Regulations (DoDGARs), DoD Manual 4160.21-M, Defense Materiel Disposition Manual, and the Cooperative Agreement between Civil Air Patrol (CAP) and the United States Air Force. It establishes CAP’s standards of property management for obtaining, controlling and disposing of all forms of CAP property. The policies presented here are necessary to ensure the availability of resources for missions and assure CAP’s compliance with directives. Guidance for proper utilization and protection of CAP property is also included. Policies contained in this regulation are directive and apply to all volunteers and units including National Staff and employees, regions, wings, groups, squadrons and flights.&lt;br /&gt;
&lt;br /&gt;
Paragraph&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Computer_Disposal&amp;diff=211</id>
		<title>Computer Disposal</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Computer_Disposal&amp;diff=211"/>
		<updated>2018-08-09T01:16:13Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Procedure for disposal of a CAP issued computer ==&lt;br /&gt;
Disposal of CAP property is addressed in CAPR 174-1. The regulation implements policies created by the Civil Air Patrol Senior Advisory Group (CSAG) and requirements contained in Congressional legislation, DoD Directive 3210.6R, DoD Grants and Agreements Regulations (DoDGARs), DoD Manual 4160.21-M, Defense Materiel Disposition Manual, and the Cooperative Agreement between Civil Air Patrol (CAP) and the United States Air Force. It establishes CAP’s standards of property management for obtaining, controlling and disposing of all forms of CAP property. The policies presented here are necessary to ensure the availability of resources for missions and assure CAP’s compliance with directives. Guidance for proper utilization and protection of CAP property is also included. Policies contained in this regulation are directive and apply to all volunteers and units including National Staff and employees, regions, wings, groups, squadrons and flights.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Main_Page&amp;diff=206</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Main_Page&amp;diff=206"/>
		<updated>2018-08-09T01:00:27Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;strong&amp;gt;Welcome to the Civil Air Patrol Wiki.&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;How to Use CAPipedia&amp;lt;/h1&amp;gt;&lt;br /&gt;
&amp;lt;big&amp;gt;&amp;lt;p&amp;gt;The search box in the upper right hand corner is your avenue to finding &lt;br /&gt;
information.&amp;amp;nbsp; Use keywords to search.&amp;amp;nbsp; If too many options come back, &lt;br /&gt;
then you can add more search words.&amp;lt;/p&amp;gt;&lt;br /&gt;
The search results are always listed below an option to create a page. Don&#039;t create a page unless no results are found.  Here is an example from a search for &amp;quot;HELPDESK&amp;quot;. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;p style=&amp;quot;border:3px; border-style:solid; border-color:#287EC7; padding: 1em;&amp;quot;&amp;gt;Create the page &amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;&amp;quot;Helpdesk&amp;quot; &amp;lt;/font&amp;gt; on this wiki! See also the search results found. &amp;lt;BR&amp;gt;&amp;lt;BR&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Page title matches &amp;lt;BR&amp;gt;&lt;br /&gt;
HelpDesk&amp;lt;BR&amp;gt;&lt;br /&gt;
== eServices HelpDesk == CAP&#039;s eServices HelpDesk can be found at this link &amp;lt;BR&amp;gt;https://capnhq.crmdesk.com/home.aspx or&lt;br /&gt;
2 KB (325 words) - 16:49, 1 August 2018&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;big&amp;gt;TIPS&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Avoid short and common words&#039;&#039;&#039;&lt;br /&gt;
This is the most likely cause of an unexpected failed search. If your search terms include a common &amp;quot;stop word&amp;quot; (such as &amp;quot;the&amp;quot;, &amp;quot;one&amp;quot;, &amp;quot;your&amp;quot;, &amp;quot;more&amp;quot;, &amp;quot;right&amp;quot;, &amp;quot;while&amp;quot;, &amp;quot;when&amp;quot;, &amp;quot;who&amp;quot;, &amp;quot;which&amp;quot;, &amp;quot;such&amp;quot;, &amp;quot;every&amp;quot;, &amp;quot;about&amp;quot;, &amp;quot;onto&amp;quot;), then your search will fail without any results. Short numbers, and words that appear in half of all pages, will also not be found. In this case, drop those words and rerun the search. &amp;lt;BR&amp;gt;&amp;lt;BR&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;Search is case-insensitive&#039;&#039;&#039;&amp;lt;BR&amp;gt;&lt;br /&gt;
The searches for &amp;quot;fortran&amp;quot;, &amp;quot;Fortran&amp;quot; and &amp;quot;FORTRAN&amp;quot; all return the same results. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Search Examples:&amp;amp;nbsp; &#039;&#039;&#039;How do I change my password?&#039;&#039;&#039;&amp;amp;nbsp;&amp;amp;nbsp; You want to &lt;br /&gt;
type &#039;&#039;&#039;password&#039;&#039;&#039; in the search box.&amp;amp;nbsp; &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/big&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Want to learn more about magic behind capmembers.wiki?  Consult the [//meta.wikimedia.org/wiki/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
* [[CAPipedia Style Guide]]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Main_Page&amp;diff=205</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Main_Page&amp;diff=205"/>
		<updated>2018-08-09T00:58:42Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;strong&amp;gt;Welcome to the Civil Air Patrol Wiki.&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h1&amp;gt;How to Use CAPipedia&amp;lt;/h1&amp;gt;&lt;br /&gt;
&amp;lt;big&amp;gt;&amp;lt;p&amp;gt;The search box in the upper right hand corner is your avenue to finding &lt;br /&gt;
information.&amp;amp;nbsp; Use keywords to search.&amp;amp;nbsp; If too many options come back, &lt;br /&gt;
then you can add more search words.&amp;lt;/p&amp;gt;&lt;br /&gt;
The search results are always listed below an option to create a page. Don&#039;t create a page unless no results are found.  Here is an example from a search for &amp;quot;HELDESK&amp;quot;. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;p style=&amp;quot;border:3px; border-style:solid; border-color:#287EC7; padding: 1em;&amp;quot;&amp;gt;Create the page &amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;&amp;quot;Helpdesk&amp;quot; &amp;lt;/font&amp;gt; on this wiki! See also the search results found. &amp;lt;BR&amp;gt;&amp;lt;BR&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Page title matches &amp;lt;BR&amp;gt;&lt;br /&gt;
HelpDesk&amp;lt;BR&amp;gt;&lt;br /&gt;
== eServices HelpDesk == CAP&#039;s eServices HelpDesk can be found at this link &amp;lt;BR&amp;gt;https://capnhq.crmdesk.com/home.aspx or&lt;br /&gt;
2 KB (325 words) - 16:49, 1 August 2018&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;big&amp;gt;TIPS&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Avoid short and common words&#039;&#039;&#039;&lt;br /&gt;
This is the most likely cause of an unexpected failed search. If your search terms include a common &amp;quot;stop word&amp;quot; (such as &amp;quot;the&amp;quot;, &amp;quot;one&amp;quot;, &amp;quot;your&amp;quot;, &amp;quot;more&amp;quot;, &amp;quot;right&amp;quot;, &amp;quot;while&amp;quot;, &amp;quot;when&amp;quot;, &amp;quot;who&amp;quot;, &amp;quot;which&amp;quot;, &amp;quot;such&amp;quot;, &amp;quot;every&amp;quot;, &amp;quot;about&amp;quot;, &amp;quot;onto&amp;quot;), then your search will fail without any results. Short numbers, and words that appear in half of all pages, will also not be found. In this case, drop those words and rerun the search. &amp;lt;BR&amp;gt;&amp;lt;BR&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;Search is case-insensitive&#039;&#039;&#039;&amp;lt;BR&amp;gt;&lt;br /&gt;
The searches for &amp;quot;fortran&amp;quot;, &amp;quot;Fortran&amp;quot; and &amp;quot;FORTRAN&amp;quot; all return the same results. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;Search Examples:&amp;amp;nbsp; &#039;&#039;&#039;How do I change my password?&#039;&#039;&#039;&amp;amp;nbsp;&amp;amp;nbsp; You want to &lt;br /&gt;
type &#039;&#039;&#039;password&#039;&#039;&#039; in the search box.&amp;amp;nbsp; &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/big&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Want to learn more about magic behind capmembers.wiki?  Consult the [//meta.wikimedia.org/wiki/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
* [[CAPipedia Style Guide]]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Internet_Operations&amp;diff=163</id>
		<title>Internet Operations</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Internet_Operations&amp;diff=163"/>
		<updated>2018-08-01T20:40:53Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== Submissions == == Approvals ==&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Submissions ==&lt;br /&gt;
== Approvals ==&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=CAPR_120-1&amp;diff=162</id>
		<title>CAPR 120-1</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=CAPR_120-1&amp;diff=162"/>
		<updated>2018-08-01T20:34:33Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP Regulation 120-1 INFORMATION TECHNOLOGY SECURITY==&lt;br /&gt;
[https://www.gocivilairpatrol.com/media/cms/CAPR_1201_Information_Technology_Se_3007CE7E168DE.pdf Civil Air Patrol Regulation 120-1]&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;This regulation establishes policies and procedures for the management of Civil Air Patrol (CAP) electronic information and data systems including, but not limited to, servers, computer network systems, personal computers, software applications, websites, web applications and data files. Responsibilities for management and use of CAP radio networks is not within the scope CAPR 120-1. This regulation is applicable to all CAP units and members.&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
== Purpose ==&lt;br /&gt;
=== 1.1. The purpose of this regulation is to ensure the security and integrity of CAP information systems and data.  This policy applies to all CAP members who have access to CAP IT assets, computer networks and corporate data and must be followed whether using CAP-owned IT assets or personal assets in the conduct of CAP business.  Effective security is a team effort involving the participation and support of every CAP member who deals with information and/or information systems.  Every computer user is responsible to know these guidelines, and to conduct his/her activities accordingly. ===&lt;br /&gt;
&lt;br /&gt;
== Roles and Definitions ==&lt;br /&gt;
=== Definitions ===&lt;br /&gt;
==== 2.1.1. CAP resources are defined as any hardware, software or computer network that is provided by the Civil Air Patrol. Where responsibilities arise to protect CAP computer networks and data accessed via personally owned computing resources, including but not limited to mobile phones, laptops and tablets, those responsibilities will be called out specifically. ====&lt;br /&gt;
==== 2.1.2. CAP Domain Operations are defined as any activity operated or conducted through the internet which makes use of a domain name that uses the name &amp;quot;Civil Air Patrol”, its insignia, copyrights, emblems, badges, descriptive or designating marks or words used in carrying out the Civil Air Patrol program. Civil Air Patrol’s names and marks are specifically owned by Civil Air Patrol pursuant to 36 United States Code § 40306.  ====&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=CAPR_120-1&amp;diff=161</id>
		<title>CAPR 120-1</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=CAPR_120-1&amp;diff=161"/>
		<updated>2018-08-01T20:33:21Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP Regulation 120-1 INFORMATION TECHNOLOGY SECURITY==&lt;br /&gt;
[https://www.gocivilairpatrol.com/media/cms/CAPR_1201_Information_Technology_Se_3007CE7E168DE.pdf Civil Air Patrol Regulation 120-1]&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This regulation establishes policies and procedures for the management of Civil Air Patrol (CAP) electronic information and data systems including, but not limited to, servers, computer network systems, personal computers, software applications, websites, web applications and data files. Responsibilities for management and use of CAP radio networks is not within the scope CAPR 120-1. This regulation is applicable to all CAP units and members.&lt;br /&gt;
&lt;br /&gt;
== Purpose ==&lt;br /&gt;
=== 1.1. The purpose of this regulation is to ensure the security and integrity of CAP information systems and data.  This policy applies to all CAP members who have access to CAP IT assets, computer networks and corporate data and must be followed whether using CAP-owned IT assets or personal assets in the conduct of CAP business.  Effective security is a team effort involving the participation and support of every CAP member who deals with information and/or information systems.  Every computer user is responsible to know these guidelines, and to conduct his/her activities accordingly. ===&lt;br /&gt;
&lt;br /&gt;
== Roles and Definitions ==&lt;br /&gt;
=== Definitions ===&lt;br /&gt;
==== 2.1.1. CAP resources are defined as any hardware, software or computer network that is provided by the Civil Air Patrol. Where responsibilities arise to protect CAP computer networks and data accessed via personally owned computing resources, including but not limited to mobile phones, laptops and tablets, those responsibilities will be called out specifically. ====&lt;br /&gt;
==== 2.1.2. CAP Domain Operations are defined as any activity operated or conducted through the internet which makes use of a domain name that uses the name &amp;quot;Civil Air Patrol”, its insignia, copyrights, emblems, badges, descriptive or designating marks or words used in carrying out the Civil Air Patrol program. Civil Air Patrol’s names and marks are specifically owned by Civil Air Patrol pursuant to 36 United States Code § 40306.  ====&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=IT_Governance&amp;diff=159</id>
		<title>IT Governance</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=IT_Governance&amp;diff=159"/>
		<updated>2018-08-01T19:59:12Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP&#039;s Information Technology Governance ==&lt;br /&gt;
&lt;br /&gt;
=== IT Executive Committee ===&lt;br /&gt;
==== Purpose ====&lt;br /&gt;
* To oversee the use of IT in support of CAP’s business strategy. &lt;br /&gt;
* Acts as an advisory group to the CEO, COO and CIO on IT related issues.&lt;br /&gt;
==== Goals ====&lt;br /&gt;
* Strategic alignment of CAP organizational and IT goals &lt;br /&gt;
* Delivering of value to the business from IT &lt;br /&gt;
* Judicious use of IT resources &lt;br /&gt;
* Management of IT related risks &lt;br /&gt;
* Measurement of IT performance &lt;br /&gt;
&lt;br /&gt;
=== IT Steering Committee ===&lt;br /&gt;
==== Purpose ====&lt;br /&gt;
The IT Steering Committee&#039;s primary responsibility is to evaluate project proposals against established criteria such as risk mitigation, breadth of impact, and regulatory requirements.  ITSC Representatives score each IT proposal resulting in a prioritized list of projects expected to bring the highest business value to Civil Air Patrol. During the bi-weekly ITSC meetings, members review which project proposals should be approved for development and assigned to a sprint.  Every attempt is made to work the highest value item; however these items are not always “ready to go” due to incomplete requirements or other timing issues.  When that occurs, a lower ranked item may be approved ahead of the higher ranked items, where its requirements are well understood.&lt;br /&gt;
&lt;br /&gt;
=== IT Functional Users Group (FUG) ===&lt;br /&gt;
==== Purpose ====&lt;br /&gt;
The primary responsibility of the FUG to identify, evaluate and assist in the prioritization of field generated requirements based on their functional expertise and broad experience with eServices.  Help desk tickets for IT enhancements and fixes with viable workarounds are automatically routed to the FUG Chair who will coordinate the group’s evaluation.  Each request will be evaluated by at least 2 FUG members and discussed during the bi-weekly FUG meeting.  Their recommendations regarding viable project proposals will be provided to the ITSC for scoring and prioritization. &lt;br /&gt;
&lt;br /&gt;
=== IT Technical Advisory Group (TAG) ===&lt;br /&gt;
==== Purpose ====&lt;br /&gt;
* Act as the liaison between members in the field and NHQ IT regarding the technical environment(s) provided to, and security requirements expected of, members in the field&lt;br /&gt;
* Advise and make recommendations to the CIO/National IT Manager regarding local: Application Innovation, Security Issues, Data Management and IT Asset Utilization&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=IT_Governance&amp;diff=158</id>
		<title>IT Governance</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=IT_Governance&amp;diff=158"/>
		<updated>2018-08-01T19:58:15Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== CAP&amp;#039;s Information Technology Governance ==  === IT Executive Committee === ==== Purpose ==== * To oversee the use of IT in support of CAP’s business strategy.  * Acts as...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP&#039;s Information Technology Governance ==&lt;br /&gt;
&lt;br /&gt;
=== IT Executive Committee ===&lt;br /&gt;
==== Purpose ====&lt;br /&gt;
* To oversee the use of IT in support of CAP’s business strategy. &lt;br /&gt;
* Acts as an advisory group to the CEO, COO and CIO on IT related issues.&lt;br /&gt;
==== Goals ====&lt;br /&gt;
* Strategic alignment of CAP organizational and IT goals &lt;br /&gt;
* Delivering of value to the business from IT &lt;br /&gt;
* Judicious use of IT resources &lt;br /&gt;
* Management of IT related risks &lt;br /&gt;
* Measurement of IT performance &lt;br /&gt;
&lt;br /&gt;
=== IT Steering Committee ===&lt;br /&gt;
==== Purpose ====&lt;br /&gt;
The IT Steering Committee&#039;s primary responsibility is to evaluate project proposals against established criteria such as risk mitigation, breadth of impact, and regulatory requirements.  ITSC Representatives score each IT proposal resulting in a prioritized list of projects expected to bring the highest business value to Civil Air Patrol. During the bi-weekly ITSC meetings, members review which project proposals should be approved for development and assigned to a sprint.  Every attempt is made to work the highest value item; however these items are not always “ready to go” due to incomplete requirements or other timing issues.  When that occurs, a lower ranked item may be approved ahead of the higher ranked items, where its requirements are well understood.&lt;br /&gt;
&lt;br /&gt;
=== IT Functional Users Group (FUG) ===&lt;br /&gt;
==== Purpose ====&lt;br /&gt;
The primary responsibility of the FUG to identify, evaluate and assist in the prioritization of field generated requirements based on their functional expertise and broad experience with eServices.  Help desk tickets for IT enhancements and fixes with viable workarounds are automatically routed to the FUG Chair who will coordinate the group’s evaluation.  Each request will be evaluated by at least 2 FUG members and discussed during the bi-weekly FUG meeting.  Their recommendations regarding viable project proposals will be provided to the ITSC for scoring and prioritization. &lt;br /&gt;
&lt;br /&gt;
=== IT Technical Advisory Group ===&lt;br /&gt;
==== Purpose ====&lt;br /&gt;
* Act as the liaison between members in the field and NHQ IT regarding the technical environment(s) provided to, and security requirements expected of, members in the field&lt;br /&gt;
* Advise and make recommendations to the CIO/National IT Manager regarding local: Application Innovation, Security Issues, Data Management and IT Asset Utilization&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Unit_Network&amp;diff=157</id>
		<title>Unit Network</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Unit_Network&amp;diff=157"/>
		<updated>2018-08-01T19:49:15Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== Best practices for setting up a Unit computer network ==&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Best practices for setting up a Unit computer network ==&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=EServices&amp;diff=156</id>
		<title>EServices</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=EServices&amp;diff=156"/>
		<updated>2018-08-01T19:45:45Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== How to create an eServices login? ==   == How to manage my eServices login? ==   == How to change my eServices password? ==&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to create an eServices login? ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== How to manage my eServices login? ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== How to change my eServices password? ==&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Collaboration_Tools&amp;diff=152</id>
		<title>Collaboration Tools</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Collaboration_Tools&amp;diff=152"/>
		<updated>2018-08-01T19:41:15Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Collaboration Tools ==&lt;br /&gt;
* Slack&lt;br /&gt;
* Google Hangout&lt;br /&gt;
* Microsoft Skype&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Collaboration_Tools&amp;diff=151</id>
		<title>Collaboration Tools</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Collaboration_Tools&amp;diff=151"/>
		<updated>2018-08-01T19:40:59Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== Collaboration Tools == &amp;lt;br&amp;gt; * Slack * Google Hangout * Microsoft Skype&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Collaboration Tools ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
* Slack&lt;br /&gt;
* Google Hangout&lt;br /&gt;
* Microsoft Skype&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Computer_Disposal&amp;diff=150</id>
		<title>Computer Disposal</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Computer_Disposal&amp;diff=150"/>
		<updated>2018-08-01T19:36:43Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== Procedure for disposal of a CAP issued computer ==&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Procedure for disposal of a CAP issued computer ==&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=About_CAP&amp;diff=148</id>
		<title>About CAP</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=About_CAP&amp;diff=148"/>
		<updated>2018-08-01T19:32:20Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;big&amp;gt;Since Civil Air Patrol’s formation during the earliest days of World War II, this vigilant organization of citizen Airmen has been committed to service to America. Founded on Dec. 1, 1941, to mobilize the nation&#039;s civilian aviation resources for national defense service, CAP has evolved into a premier public service organization that still carries out emergency service missions when needed — in the air and on the ground.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As a Total Force partner and Auxiliary of the U.S. Air Force, Civil Air Patrol is there to search for and find the lost, provide comfort in times of disaster and work to keep the homeland safe. Its 60,000 members selflessly devote their time, energy and expertise toward the well-being of their communities, while also promoting aviation and related fields through aerospace/STEM education and helping shape future leaders through CAP’s cadet program.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Civil Air Patrol’s missions for America are many, and today’s adults and cadets perform their duties with the same vigilance as its founding members — preserving CAP’s 75-year legacy of service while maintaining its commitment to nearly 1,500 communities nationwide.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;/big&amp;gt;&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Vision_Statement&amp;diff=147</id>
		<title>Vision Statement</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Vision_Statement&amp;diff=147"/>
		<updated>2018-08-01T19:31:34Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP&#039;s Vision Statement ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;big&amp;gt;Civil Air Patrol, America&#039;s Air Force auxiliary, building the nation&#039;s finest force of citizen volunteers serving America.&lt;br /&gt;
&amp;lt;/big&amp;gt;&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Vision_Statement&amp;diff=146</id>
		<title>Vision Statement</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Vision_Statement&amp;diff=146"/>
		<updated>2018-08-01T19:31:09Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP&#039;s Vision Statement ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;big&amp;gt;Big text&amp;lt;/big&amp;gt;Civil Air Patrol, America&#039;s Air Force auxiliary, building the nation&#039;s finest force of citizen volunteers serving America.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Vision_Statement&amp;diff=144</id>
		<title>Vision Statement</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Vision_Statement&amp;diff=144"/>
		<updated>2018-08-01T19:30:29Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== CAP&amp;#039;s Vision Statement ==  Civil Air Patrol, America&amp;#039;s Air Force auxiliary, building the nation&amp;#039;s finest force of citizen volunteers serving America.&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP&#039;s Vision Statement ==&lt;br /&gt;
&lt;br /&gt;
Civil Air Patrol, America&#039;s Air Force auxiliary, building the nation&#039;s finest force of citizen volunteers serving America.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=About_CAP&amp;diff=143</id>
		<title>About CAP</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=About_CAP&amp;diff=143"/>
		<updated>2018-08-01T19:29:34Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;Since Civil Air Patrol’s formation during the earliest days of World War II, this vigilant organization of citizen Airmen has been committed to service to America. Founded o...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Since Civil Air Patrol’s formation during the earliest days of World War II, this vigilant organization of citizen Airmen has been committed to service to America. Founded on Dec. 1, 1941, to mobilize the nation&#039;s civilian aviation resources for national defense service, CAP has evolved into a premier public service organization that still carries out emergency service missions when needed — in the air and on the ground.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As a Total Force partner and Auxiliary of the U.S. Air Force, Civil Air Patrol is there to search for and find the lost, provide comfort in times of disaster and work to keep the homeland safe. Its 60,000 members selflessly devote their time, energy and expertise toward the well-being of their communities, while also promoting aviation and related fields through aerospace/STEM education and helping shape future leaders through CAP’s cadet program.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Civil Air Patrol’s missions for America are many, and today’s adults and cadets perform their duties with the same vigilance as its founding members — preserving CAP’s 75-year legacy of service while maintaining its commitment to nearly 1,500 communities nationwide.&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Mission_Statement&amp;diff=142</id>
		<title>Mission Statement</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Mission_Statement&amp;diff=142"/>
		<updated>2018-08-01T19:28:09Z</updated>

		<summary type="html">&lt;p&gt;BReady72: /* CAP Mission Statement */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP&#039;s Mission Statement ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;big&amp;gt;Supporting America&#039;s communities with emergency response, diverse aviation and ground services, youth development, and promotion of air, space, and cyber power.&amp;lt;/big&amp;gt;&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Mission_Statement&amp;diff=141</id>
		<title>Mission Statement</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Mission_Statement&amp;diff=141"/>
		<updated>2018-08-01T19:27:52Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== CAP Mission Statement ==  &amp;lt;big&amp;gt;Supporting America&amp;#039;s communities with emergency response, diverse aviation and ground services, youth development, and promotion of air, spac...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP Mission Statement ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;big&amp;gt;Supporting America&#039;s communities with emergency response, diverse aviation and ground services, youth development, and promotion of air, space, and cyber power.&amp;lt;/big&amp;gt;&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=National_Conference&amp;diff=140</id>
		<title>National Conference</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=National_Conference&amp;diff=140"/>
		<updated>2018-08-01T19:26:56Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP National Conference ==&lt;br /&gt;
=== Anaheim, California August 23-25, 2018 ===&lt;br /&gt;
&lt;br /&gt;
More information can be found at [https://www.gocivilairpatrol.com/members/events/conference/ National Conference 2018].&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=National_Conference&amp;diff=139</id>
		<title>National Conference</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=National_Conference&amp;diff=139"/>
		<updated>2018-08-01T19:25:44Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== CAP National Conference == === Anaheim, California August 23-25, 2018 ===  More information can be found [https://www.gocivilairpatrol.com/members/events/conference/ Nation...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP National Conference ==&lt;br /&gt;
=== Anaheim, California August 23-25, 2018 ===&lt;br /&gt;
&lt;br /&gt;
More information can be found [https://www.gocivilairpatrol.com/members/events/conference/ National Conference 2018].&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=2018_Field_Computer&amp;diff=131</id>
		<title>2018 Field Computer</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=2018_Field_Computer&amp;diff=131"/>
		<updated>2018-08-01T19:07:43Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== 2018 Field Computer Specifications ==  * 8th Gen Intel Core i7-8650U (8M Cache, Quad Core, 1.9GHz), vPro * Win 10 Pro 64 English, French, Spanish * Microsoft(R) Office 30 D...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 2018 Field Computer Specifications ==&lt;br /&gt;
&lt;br /&gt;
* 8th Gen Intel Core i7-8650U (8M Cache, Quad Core, 1.9GHz), vPro&lt;br /&gt;
* Win 10 Pro 64 English, French, Spanish&lt;br /&gt;
* Microsoft(R) Office 30 Days Trial&lt;br /&gt;
* Intel(R) Core(TM) i7-8650U Processor Base, Integrated UHD Graphics 620&lt;br /&gt;
* 16GB, 1x16GB, 2400Mhz DDR4 Memory&lt;br /&gt;
* 2.5&amp;quot; 500GB SATA 7200 RPM Hard Drive&lt;br /&gt;
* 7MM HDD/SSD Hard Drive &lt;br /&gt;
* Non-Touch LCD Back Cover with WLAN antenna&lt;br /&gt;
* Non-Touch LCD bezel+RGB(HD) camera+Mic&lt;br /&gt;
* 15.6&amp;quot; HD (1366 x 768) Non-Touch LCD&lt;br /&gt;
* Dual Pointing English Qwerty Keyboard&lt;br /&gt;
* No Mouse&lt;br /&gt;
* Intel Dual-Band Wireless-AC 8265 Driver&lt;br /&gt;
* Intel Dual Band Wireless AC 8265 (802.11ac) 2x2 + Bluetooth 4.2&lt;br /&gt;
* No Wireless WWAN Card&lt;br /&gt;
* Primary 4-cell 68W/HR Battery&lt;br /&gt;
* 65W AC Adapter, 3-pin&lt;br /&gt;
* Dual Point Palmrest with Full Security + FP_DigitalPersona-FIPS&lt;br /&gt;
* No Anti-Virus Software&lt;br /&gt;
* No Media&lt;br /&gt;
* No FGA&lt;br /&gt;
* US Power Cord&lt;br /&gt;
* Waves Maxx Audio&lt;br /&gt;
* No Carrying Case&lt;br /&gt;
* No Removable CD/DVD Drive&lt;br /&gt;
* Energy Star 6.1&lt;br /&gt;
* No Docking Station&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Compliance_Inspection&amp;diff=124</id>
		<title>Compliance Inspection</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Compliance_Inspection&amp;diff=124"/>
		<updated>2018-08-01T18:58:22Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== D-9 Information Technology&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
=== Question 01&amp;lt;br&amp;gt; ===&lt;br /&gt;
Has the wing published any supplements or operating instructions, or requested and been granted any waivers to [[CAPR 120-1]]? &lt;br /&gt;
# Is the wing operating under any supplements or operating instructions to [[CAPR 120-1]], and, if so, were they approved IAW this regulation prior to implementation?&lt;br /&gt;
# Is the wing operating under any waiver to [[CAPR 120-1]] and, if so, were they approved IAW this regulation prior to implementation?&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Compare wing’s published supplements/OIs or waivers with those documents posted on the CAP publication website.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Question 02&amp;lt;br&amp;gt; ===&lt;br /&gt;
Does the Wing have an assigned Director of IT or IT&lt;br /&gt;
# Officer responsible for maintenance, upkeep and compliance with regard to use of all CAP IT assets within their respective units IAW [[CAPR 120-1 Paragraph 2.2.5|CAPR 120-1 para 2.2.5]]?&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Review duty assignments for the wing within eServices to identify whether the Wing has an assigned Director of IT or IT Officer.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Question 03&amp;lt;br&amp;gt; ===&lt;br /&gt;
# Are all wing CAP Internet Operations records current IAW [[CAPR 120-1 Paragraph 5.2.2|CAPR 120-1 para 5.2.2]]?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Review the Internet Operations Report and the Organizational Report from Members Reports to determine if all websites are approved and approval dates for Wing websites are within the current fiscal year.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Question 04&amp;lt;br&amp;gt; ===&lt;br /&gt;
# Are locally developed web pages dealing with confidential information clearly marked with the warning required by [[CAPR 120-1 Paragraph 9.2.4|CAPR 120-1 para 9.2.4]]?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Review representational sample of unit web pages noting whether warning is present when the page is displaying confidential information.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Question 05 &amp;lt;br&amp;gt; ===&lt;br /&gt;
# Are backups of electronic files made IAW [[CAPR 120-1 Paragraph 11.6|CAPR 120-1 para 11.6]]?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Review unit’s backup schedule documentation to ensure backups are being completed IAW [[CAPR 120-1 Paragraph 11.6|CAPR 120-1 para 11.6]]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Question 06&amp;lt;br&amp;gt; ===&lt;br /&gt;
# Are the default anti-virus protections enabled on all CAP issued computers IAW [[CAPR 120-1 Paragraph 11.7|CAPR 120-1 para 11.7]]?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Review a representative sample of locally available CAP issued laptops for current anti-virus software. &lt;br /&gt;
 This can found by navigating to the right hand corner of the task bar, &lt;br /&gt;
 Locating the anti-virus software icon &lt;br /&gt;
 Opening application to identify if services are current and active&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Compliance_Inspection&amp;diff=123</id>
		<title>Compliance Inspection</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Compliance_Inspection&amp;diff=123"/>
		<updated>2018-08-01T18:57:59Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== D-9 Information Technology&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
=== Question 01&amp;lt;br&amp;gt; ===&lt;br /&gt;
Has the wing published any supplements or operating instructions, or requested and been granted any waivers to [[CAPR 120-1]]? &lt;br /&gt;
# Is the wing operating under any supplements or operating instructions to [[CAPR 120-1]], and, if so, were they approved IAW this regulation prior to implementation?&lt;br /&gt;
# Is the wing operating under any waiver to [[CAPR 120-1]] and, if so, were they approved IAW this regulation prior to implementation?&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Compare wing’s published supplements/OIs or waivers with those documents posted on the CAP publication website.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Question 02&amp;lt;br&amp;gt; ===&lt;br /&gt;
Does the Wing have an assigned Director of IT or IT&lt;br /&gt;
# Officer responsible for maintenance, upkeep and compliance with regard to use of all CAP IT assets within their respective units IAW [[CAPR 120-1 Paragraph 2.2.5|CAPR 120-1 para 2.2.5]]?&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Review duty assignments for the wing within eServices to identify whether the Wing has an assigned Director of IT or IT Officer.&lt;br /&gt;
&lt;br /&gt;
=== Question 03&amp;lt;br&amp;gt; ===&lt;br /&gt;
# Are all wing CAP Internet Operations records current IAW [[CAPR 120-1 Paragraph 5.2.2|CAPR 120-1 para 5.2.2]]?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Review the Internet Operations Report and the Organizational Report from Members Reports to determine if all websites are approved and approval dates for Wing websites are within the current fiscal year.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Question 04&amp;lt;br&amp;gt; ===&lt;br /&gt;
# Are locally developed web pages dealing with confidential information clearly marked with the warning required by [[CAPR 120-1 Paragraph 9.2.4|CAPR 120-1 para 9.2.4]]?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Review representational sample of unit web pages noting whether warning is present when the page is displaying confidential information.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Question 05 &amp;lt;br&amp;gt; ===&lt;br /&gt;
# Are backups of electronic files made IAW [[CAPR 120-1 Paragraph 11.6|CAPR 120-1 para 11.6]]?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Review unit’s backup schedule documentation to ensure backups are being completed IAW [[CAPR 120-1 Paragraph 11.6|CAPR 120-1 para 11.6]]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Question 06&amp;lt;br&amp;gt; ===&lt;br /&gt;
# Are the default anti-virus protections enabled on all CAP issued computers IAW [[CAPR 120-1 Paragraph 11.7|CAPR 120-1 para 11.7]]?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
How to verify compliance?&amp;lt;br&amp;gt;&lt;br /&gt;
 Review a representative sample of locally available CAP issued laptops for current anti-virus software. &lt;br /&gt;
 This can found by navigating to the right hand corner of the task bar, &lt;br /&gt;
 Locating the anti-virus software icon &lt;br /&gt;
 Opening application to identify if services are current and active&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Non-Profit_Software&amp;diff=121</id>
		<title>Non-Profit Software</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Non-Profit_Software&amp;diff=121"/>
		<updated>2018-08-01T18:18:21Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP Non-profit Pricing ==&lt;br /&gt;
&lt;br /&gt;
In many cases CAP is eligible for non-profit pricing for software and IT services.&lt;br /&gt;
&lt;br /&gt;
* Google eSuite&lt;br /&gt;
* Microsoft 365&lt;br /&gt;
* Tech Soup&lt;br /&gt;
* Join.me&lt;br /&gt;
* GoToMeeting&lt;br /&gt;
&lt;br /&gt;
Units should contact their Wing IT staff for more details.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Non-Profit_Software&amp;diff=120</id>
		<title>Non-Profit Software</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Non-Profit_Software&amp;diff=120"/>
		<updated>2018-08-01T18:18:01Z</updated>

		<summary type="html">&lt;p&gt;BReady72: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP eligible for Non-profit Pricing ==&lt;br /&gt;
&lt;br /&gt;
In many cases CAP is eligible for non-profit pricing for software and IT services.&lt;br /&gt;
&lt;br /&gt;
* Google eSuite&lt;br /&gt;
* Microsoft 365&lt;br /&gt;
* Tech Soup&lt;br /&gt;
* Join.me&lt;br /&gt;
* GoToMeeting&lt;br /&gt;
&lt;br /&gt;
Units should contact their Wing IT staff for more details.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=Non-Profit_Software&amp;diff=119</id>
		<title>Non-Profit Software</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=Non-Profit_Software&amp;diff=119"/>
		<updated>2018-08-01T18:17:00Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== CAP maybe eligible for Non-profit Pricing ==  In many cases CAP is legible for non-profit pricing for software and IT services.  * Google eSuite * Microsoft 365 * Tech Soup...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== CAP maybe eligible for Non-profit Pricing ==&lt;br /&gt;
&lt;br /&gt;
In many cases CAP is legible for non-profit pricing for software and IT services.&lt;br /&gt;
&lt;br /&gt;
* Google eSuite&lt;br /&gt;
* Microsoft 365&lt;br /&gt;
* Tech Soup&lt;br /&gt;
* Join.me&lt;br /&gt;
* GoToMeeting&lt;br /&gt;
&lt;br /&gt;
Units should contact their Wing IT staff for more details.&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
	<entry>
		<id>https://sandbox.capmembers.wiki/index.php?title=HelpDesk&amp;diff=118</id>
		<title>HelpDesk</title>
		<link rel="alternate" type="text/html" href="https://sandbox.capmembers.wiki/index.php?title=HelpDesk&amp;diff=118"/>
		<updated>2018-08-01T18:03:13Z</updated>

		<summary type="html">&lt;p&gt;BReady72: Created page with &amp;quot;== eServices HelpDesk == &amp;lt;br&amp;gt; CAP&amp;#039;s eServices HelpDesk can be found at this link https://capnhq.crmdesk.com/home.aspx&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== eServices HelpDesk ==&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
CAP&#039;s eServices HelpDesk can be found at this link https://capnhq.crmdesk.com/home.aspx&lt;/div&gt;</summary>
		<author><name>BReady72</name></author>
	</entry>
</feed>