18_RFP_Attachment_2_DD254.pdf
PDF 114 KB Posted
- Attached to
- Pacific Air Force (PACAF) Enhanced Cyber Resiliency Experienced Workforce (CREW) Federal contract opportunity
- Solicitation number
- HC1019-19-R-0003
- Issued by
- Defense Information Systems Agency
About this file
RFP Attachment 2 DD254
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| HC1019-19-R-0003_Amendment_0001.docx | DOCX document | |
| 18_RFP_Attachment_7_Questions_Answers_23_May.xlsx | XLSX spreadsheet | |
| 18_RFP_Attachment_3_Pricing_Worksheet_23_May.xlsx | XLSX spreadsheet | |
| HC1019-19-R-0003.docx | DOCX document | |
| 18_RFP_Attachment_5_BVTO_Eval_TAble_w_Full_PP_Rating.docx | DOCX document | |
| 18_RFP_Attachment_4_Past_Performance_References.doc | DOC document | |
| 18_RFP_Attachment_6_Questions_Template.xlsx | XLSX spreadsheet | |
| 18_RFP_Attachment_1_QASP.doc | DOC document | |
| 18_RFP_Attachment_3_Pricing_Worksheet.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Please wait...
If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.
You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.
For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Attachment: 1 of 3 for DD Form 254
Contract#:
Contract Expiration Date:
CONTROLLED UNCLASSIFIED INFORMATION ADDENDUM
General: There are types of information that are not classified but require application of access and distribution controls and protective measures developed for DoD Controlled Unclassified Information for a variety of reasons. The types of CUI identified for the program are For Official Use Only (FOUO), Law Enforcement Sensitive (LES), DoD Unclassified Controlled Nuclear Information (DoD UCNI), and LIMITED DISTRIBUTION as well as some of those developed by other Executive Branch agencies of the U.S. Government and technical data described below as well as protective measures for CUI material.
For Official Use Only (FOUO) Information Description: Is a Government protective marking/caveat designation applied to unclassified information that may be exempt from mandatory release to the public because of foreseeable harm to an interest protected by the Freedom of Information Act (FOIA), as implemented by DoD 5400.7-R and/or the Privacy Act of 1974, as amended.
Law Enforcement Sensitive (LES): A marking sometimes applied, in addition to the marking “FOR OFFICIAL USE ONLY,” by the Department of Justice and other activities in the law enforcement community, including those within the Department of Defense to denote that the information was compiled for law enforcement purposes and should be afforded security in order to protect certain legitimate government interests. Procedures can be found in DoDM 5200.01-V4, Enclosure 3.
DoD Unclassified Controlled Nuclear Information (DoD UCNI): Unclassified information on security measures (including security plans, procedures, and equipment) for the physical protection of DoD Special Nuclear Material (SNM), SNM equipment, SNM facilities, or nuclear weapons in DoD custody. Information is designated DoD UCNI in accordance with DoDD 5210.83.
LIMITED DISTRIBUTION: Caveat used by the National Geospatial-Intelligence Agency (NGA) to identify a select group of sensitive, unclassified imagery or geospatial information and data created or distributed by NGA or information, data, and products derived from such information. DoDI 5030.59 contains details of policies and procedures.
Technical Data Description: Any recorded information related to experimental, developmental, or engineering works that can be used to define an engineering or manufacturing process, or can be used to design, procure, produce, support, maintain, operate, repair, or overhaul program material. The data may be graphic or pictorial delineations in media (e.g., computer software, drawings, photographs, etc.), text in specifications, related performance or design documents, or computer printouts. Examples of technical data include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, catalog-item identifications, related information, and computer software documentation. The DoD Scientific and Technical Information Program (see DoDI 3200.12.).
CUI Markings: Prescribed marking of CUI documents will be in accordance with DoDM 5200.01-Vol 4. CUI may also be identified in security classification guides to ensure the information receives appropriate protection.
Access: CUI may be released to an individual who has a valid need for such access within the scope of their assigned duties, furthering the accomplishment of a lawful and authorized government purpose and would not be detrimental to the interests of the DoD or U.S. Government. Information in any media format will be disseminated on a need-to-know basis. This restricts the use or dissemination of CUI data to those with direct affiliation with the given program/project to conduct official business for the DoD, provided that dissemination is consistent with any further controls imposed by a distribution statement. Personnel no longer requiring access to CUI must surrender any information in their possession to the program lead, who will take action to terminate further access.
Storing and Handling: During working hours, take reasonable steps to minimize the risk of access to CUI by unauthorized personnel (e.g., not reading, discussing, leaving FOUO information unattended where unauthorized personnel are present or display CUI in public places to include the internet). After working hours, store CUI information in locked desks, file cabinets, bookcases, locked rooms, locked/controlled e-files or similar means to prevent theft of program information. Computers used to process CUI do not need to be accredited for classified use. Do not process CUI on public computers (e.g., those available to the public in kiosks, hotels, café’s, etc.) or computers that do not have Public Key Infrastructure (PKI) access controls. Personally owned computers are not authorized to process CUI. Authorized electronic devices provided by the government agency (e.g., laptops, cell phone) used to store CUI must be physically protected and use NIST/NIAP-approved cryptographic products, e.g., DoD approved PKI Certification available at http://iase.disa.mil/pki/eca or http://csrc.nist.gov/cryptval/, which require encryption passcodes to teleconferences/web conferences where CUI may be discussed.
Dissemination: CUI printed documents and material may be transmitted through mail channels or hand-carried without formal courier orders. CUI information may be disseminated to DoD personnel and DoD contractors to conduct official business for the program. If dissemination is required outside of DoD channels contact the program lead, contracting officer, and security manager for approval. Release of technical data will follow the release instructions identified in the distribution statement. Use secure communications whenever available for discussions involving CUI. Send voice and facsimile transmissions only when authorized recipients have acknowledged positive control measures are in place to receive the information.
Destruction: CUI documents shall be disposed of according to provisions of EO 13556, CUI; DoDM 5200.01 Vol 4, DoD Information Security Program CUI; AFI 33-332. Component records management directives. Non-record FOUO documents may be destroyed by any methods that prevents compromise, e.g., tearing, burning, or shredding of the means approved for the destruction of classified information or by any other means that would make it difficult to recognize or reconstruct the information.
Reporting: Report any loss or unauthorized attempt to gain access to CUI information to the organization’s security manager immediately, but no later than the end of the first duty day. If additional information is required after initial notification, guidance will be provided at that time.
Attachment: 2 of 3 to DD Form 254
Contract:
Contract Expiration Date:
FOR OFFICIAL USE ONLY (FOUO) ADDENDUM
The following procedures will be used to protect FOR OFFICIAL USE ONLY (FOUO) material:
HANDLING: Access to FOUO material shall be limited to those employees needing the material to do their jobs. The FOUO marking is assigned to material created by a DoD user agency. FOUO is not a classification, but requires extra precaution to ensure it is not released to the public.
MARKING: Mark unclassified documents containing FOUO, “FOR OFFICIAL USE ONLY” at the bottom of each page and back cover (if any). In a classified document, mark:
a. An individual paragraph that contains FOUO, but not classified material by placing “FOUO” at the beginning of the paragraph.
b. The top and bottom of each page that has both FOUO and classified material with the highest security classification of the material on that page.
c. “FOUO” at the bottom of each page that has FOUO but not classified material.
d. If a classified document also contains FOUO material or if the classified material becomes FOUO when declassified, place the following statement on the bottom of the cover or the first page under the classified marking: “NOTE: If declassified, review the document to make sure material is not FOUO and not exempt under AFI 37-131 before public release.”
e. Mark other records such as computer printouts, photographs, films, tapes, or slides “FOR OFFICIAL USE ONLY” so the receiver or viewer knows the record contains FOUO material.
f. Mark each part of a message that contains FOUO material. Unclassified messages containing FOUO material must show the abbreviation “FOUO” before the text begins.
g. Insure documents that transmit FOUO material call attention to any FOUO attachment.
h. FOUO material released to a contractor by a DoD user agency must have the following statement on the front page or cover: “THIS DOCUMENT CONTAINS MATERIAL EXEMPT FROM MANDATORY DISCLOSURE UNDER THE FREEDOM OF INFORMATION ACT.
STORAGE: During normal duty hours, place FOUO material in an out-of-sight location, if your work area is accessible to persons who do not have a valid need for the material. After normal duty hours, store FOUO material to prevent unauthorized access. File with other unclassified records in unlocked files or desks when internal building security is provided. When there is not internal security, locked buildings or rooms usually provide adequate after-hours protection. For additional protection, store FOUO material in locked container such a file cabinets, desks, or bookcases. Expenditures of funds for security container or close area solely for the protection of FOUO material is prohibited.
TRANSMISSION: All FOUO material transmitted via e-mail must be encrypted. Discussion of all FOUO material must be via secure telecommunications. FOUO material may be transmitted over telephone lines in digital form, via fax, or DSN lines without encryption.
RELEASE: FOUO material shall not be released outside the government except to representatives of the DoD and approved by the Government Program/Project Manager.
DESTRUCTION: When no longer needed, FOUO material shall be disposed of by a method that precludes its disclosure to unauthorized individuals by any of the means approved for the destruction of classified information or by any other means that would make it difficult to recognize or reconstruct the information.
Attachment: 3 of 3 to DD Form 254
Contract:
Awarded Date:
OPERATION SECURITY (OPSEC) ADDENDUM
1. This section outlines the requirements and procedures necessary for contractors to provide Operations Security (OPSEC) protection for PACAF's critical information.
2. OPSEC is the process of identifying, analyzing and controlling critical information indicating friendly actions attendant to military operations and other activities to:
a. Identify those actions that can be observed by adversary intelligence systems.
b. Determine what indicators adversary intelligence systems might obtain that could be interpret or pieced together to derive critical information in time to be useful to adversaries.
c. Select and execute countermeasures that eliminate or reduce to an acceptable level the vulnerabilities of friendly actions to adversary exploitation.
3. OPSEC principles are used to help assigned personnel:
a. Maintain a continuing awareness of adversary interest in SOF actions and adversary intelligence collection capabilities.
b. To understand the need to identify and protect classified and unclassified indicators that reveal sensitive information.
c. To evaluate the effectiveness of OPSEC measures taken to preclude or reduce adversary acquisition and exploitation of sensitive information.
4. Objectives are to:
a. Protect planned operational activities by preventing the inadvertent disclosure of unclassified information relating to or revealing a possible classified operation.
b. To preserve secrecy concerning specific scenario events and a PACAF response to these events.
c. To identify OPSEC vulnerabilities and recommend protective measures which will serve to enhance the security of future operations.
5. PACAF employed contractors will be provided unit-specific OPSEC education training by the assigned unit/ directorate's OPSEC program manager/coordinator on the unit/directorate's OPSEC requirements before being given full access to or around a PACAF installation, organization, facility or information, but not more than 30 days prior to initial access. Individual training will be developed and applied as required by the level of contact with PACAF critical information.
6. The contractor shall provide operation security (OPSEC) protection for all sensitive and/or critical information as defined by DoD 5205.2 and the Air Force Instruction (AFI) 10-701 and all applicable supplements.
7. The contractor shall describe the steps necessary to protect sensitive and/or critical information. The OPSEC Program Manager will evaluate the OPSEC posture of the contract activities and operations.
8. The contractor is required to follow the provisions of the organizations pre-existing OPSEC Plan. A copy of the plan (or relevant portions thereof) and the approved Critical Information List (CIL) will be provided to assigned contractors upon inprocessing so that the contractor is aware of the critical information to be protected and the OPSEC measures expected during contract performance.
9. In the event the Government agency does not require compliance with a tailored written OPSEC plan, these OPSEC measures have been prescribed:
a. Annual contractor employee OPSEC awareness briefings
b. Approval of all press releases via proper government channel prior to release.
c. Shredding of paper waste that contain critical information or may be indicators thereof
d. Report/notification of any newly identified critical information, change in personnel or environmental threat or vulnerability to government agency.
10) Additional guidance and discussion of OPSEC contents may be found at www.ioss.gov/Library Resources/ Operations Security Joint Publication 3-13.3.
DRAFT
SAMPLE
PREVIOUS EDITION IS OBSOLETE.
Page of AEM LiveCycle Designer
DD FORM 254, APR 2018
NEEDS DD67
DEPARTMENT OF DEFENSE
CONTRACT SECURITY CLASSIFICATION SPECIFICATION
(The requirements of the National Industrial Security Program (NISP) apply to all security aspects of this effort involving classified information.)
OMB No. 0704-0567 OMB approval expires:
October 31, 2020 The public reporting burden for this collection of information, 0704-0567, is estimated to average 70 minutes per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Washington Headquarters Services, at whs.mc-alex.esd.mbx.dd-dod-information-collections@mail.mil. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.
RETURN COMPLETED FORM AS DIRECTED IN THE INSTRUCTIONS.
1. CLEARANCE AND SAFEGUARDING
2. THIS SPECIFICATION IS FOR: (X and complete as applicable.)
3. THIS SPECIFICATION IS: (X and complete as applicable.)
a. ORIGINAL (Complete date in all cases.)
b. REVISED (Supersedes all previous specifications.)
4. IS THIS A FOLLOW-ON CONTRACT?
If yes, complete the following:
Classified material received or generated under
5. IS THIS A FINAL DD FORM 254?
If yes, complete the following:
6. CONTRACTOR (Include Commercial and Government Entity (CAGE) Code)
7. SUBCONTRACTOR(S) (Click button if you choose to add or list the subcontractors -- but will still require a separate DD Form 254 issued by a prime contractor to each subcontractor)
8. ACTUAL PERFORMANCE (Click button to add more locations.)
10. CONTRACTOR WILL REQUIRE ACCESS TO: (X all that apply. Provide details in Blocks 13 or 14 as set forth in the instructions.)
e. NATIONAL INTELLIGENCE INFORMATION:
11. IN PERFORMING THIS CONTRACT, THE CONTRACTOR WILL: (X all that apply. See instructions. Provide details in Blocks 13 or 14 as set forth in the instructions.)
12. PUBLIC RELEASE
Any information (classified or unclassified) pertaining to this contract shall not be released for public dissemination except as provided by the National Industrial Security Program Operating Manual (NISPOM) or unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for review and approval prior to release to the appropriate government approval authority identified here with at least office and phone contact information and if available, an e-mail address. (See instructions)
13. SECURITY GUIDANCE
The security classification guidance for classified information needed for this effort is identified below. If any difficulty is encountered in applying this guidance or if any other contributing factor indicates a need for changes in this guidance, the contractor is authorized and encouraged to provide recommended changes; to challenge the guidance or the classification assigned to any information or material furnished or generated under this contract; and to submit any questions for interpretation of this guidance to the official identified below. Pending final decision, the information involved shall be handled and protected at the highest level of classification assigned or recommended.
(Fill in as appropriate for the classified effort. Attach, or forward under separate correspondence, any documents/guides/extracts referenced herein. The field will expand as text is added. When removing any expanded text area, use delete key or backspace key, then click out of the text field for it to shrink after the text has been deleted. Also allows for up to 6 internal reviewers to digitally sign. See instructions for additional guidance or use of the fillable PDF.)
14. ADDITIONAL SECURITY REQUIREMENTS
Requirements, in addition to NISPOM requirements for classified information, are established for this contract.
If Yes, identify the pertinent contractual clauses in the contract document itself, or provide an appropriate statement which identifies the additional requirements. Provide a copy of the requirements to the CSO. The field will expand as text is added or you can also use item 13. When removing any expanded text area, use delete key or backspace key, then click out of the text field for it to shrink after the text has been deleted. (See instructions for additional guidance or use of the fillable PDF.)
15. INSPECTIONS
Elements of this contract are outside the inspection responsibility of the CSO.
If Yes, explain and identify specific areas and government activity responsible for inspections. The field will expand as text is added or you can also use item 13. When removing any expanded text area, use delete key or backspace key, then click out of the text field for it to shrink after the text has been deleted. (See instructions for additional guidance or use of the fillable PDF.)
16. GOVERNMENT CONTRACTING ACTIVITY (GCA) AND POINT OF CONTACT (POC)
17. CERTIFICATION AND SIGNATURES
Security requirements stated herein are complete and adequate for safeguarding the classified information to be released or generated under this classified effort. All questions shall be referred to the official named below. Upon digitally signing Item 17h, no changes can be made as the form will be locked.
18. REQUIRED DISTRIBUTION BY THE CERTIFYING OFFICIAL
9.0.0.2.20120627.2.874785 DD 254, DoD Contract Security Classification Specification List of Attachments [3] (All Files Must be Attached Prior to Signing, i.e., for any digital signature on the form) Addendum 1 CUI Addendum.docx Addendum 2 FOUO.docx Addendum 3 Operation Security.docx
| CurrentPage: |
| PageCount: |
| Classification: Unclassified |
| SerialNum: |
| a. Facility clearance level. Select one.: 2 |
| b. Level of safeguarding for classified information/material required at contractor facility. Select one.: 4 |
| Choose Yes or No: 0 |
| Choose Yes or No: 1 |
| Prime: |
| Choose Yes or No: 0 |
| Choose Yes or No: 0 |
| Sub: |
| Choose Yes or No: 0 |
| Choose Yes or No: 0 |
| Soli: |
| DueDate: |
| dateA: |
| RevisionNum: |
| dateB: |
| Final: |
| dateC: |
| No: 1 |
| No: 1 |
| No: 1 |
| No: 1 |
| Yes: 0 |
| Yes: 0 |
| Yes: 0 |
| Yes: 0 |
| Enter your name here.: |
| ReqDated: |
| Enter your name here.: |
| Name: |
| Cage: |
| CSO: |
| addrow: |
| Removerow: |
| Click to delete a row: |
| Location: DOD facilities where classified is processed, discussed, created, transmitted, or stored. See section 13. |
| Block9: Contractor will provide thirteen (13) full time personnel to work at Ten (10) Main Operating Bases (MOBs) that will upgrade/enhance/maintain the End User Computing (EUC) environment through the enhancement/management of the PACAF enterprise Virtual Environment of all Air Force circuits/enclaves utilized by PACAF's Bases and selected Geographically Separated Units (GSUs). Locations are are outlined in the Performance Work Statement (PWS). |
| a: 0 |
| a: 1 |
| a: 0 |
| f: 0 |
| f: 0 |
| f: 0 |
| b: 0 |
| b: 0 |
| b: 0 |
| g: 0 |
| g: 0 |
| c: 0 |
| c: 0 |
| c: 0 |
| h: 0 |
| h: 0 |
| d: 0 |
| d: 0 |
| d: 0 |
| i: 0 |
| i: 0 |
| SCI: 0 |
| NonSCI: 0 |
| j: 1 |
| j: 1 |
| k: 1 |
| k: 0 |
| Enter your name here.: FOUO Information & NIPR/SIPRNet access required (Block 13) |
| e: 1 |
| e: 0 |
| l: 0 |
| m: 0 |
| direct: 0 |
| thru: 1 |
| Enter your name here.: The GCA CO/COR/COTR for higher approval prior to public release. |
| PublicAuthority: NI 5720.1, DoD, 5105.21-M-1, Chapter 1 & DoD 5220.22M, Chapter 5 |
| AddSig: |
| RemoveSig: |
| text: Ref 8 Actual Performance Locations: |
Joint Base Pearl Harbor-Hickam, Hawaii Joint Base Elmendorf Richardson, Alaska Eielson AB, Alaska Andersen AFB, Guam Osan AB, Korea Kunsan AB, Korea Kadena AB, Okinawa Japan Yokota AFB, Japan Misawa AB, Japan Diego Garcia
Actual Performance: The highest level of security clearance required for contract performance is SECRET. The government will oversee the handling and storage of classified information in support of this contract. All classified information will be returned to the government upon termination of the contract.
Ref 10j. FOUO information: The Contractor is authorized and may have access to UNCLASSIFIED information/material identified as "FOR OFFICIAL USE ONLY" (FOUO). The contractor is prohibited from further disclosure/dissemination of this information without authorization. Material identified as FOUO shall be safeguarded IAW the guidance contained in DoD 5200.1-R, Appendix 3, Information Security Program. In addition, contractors or subcontractors must obtain approval from the GCA CO/COR or HQ PACAF/Public Affairs prior to posting any unclassified information that was provided to them on web site or the Internet. GCA must provide guidance on protection procedures in Item 13. IAW OPSEC and Security Planning, information shall be stored and processed on information systems approved for “For Official Use Only” data that provide password or PKI protection. Web sites shall implement secure connections (i.e., https/SSL) and require user identification for access (i.e., password/ID or PKI). (DoD Regulation 5400.7, DoD Freedom of Information Act Program).
Ref 10k The government will provide classified network access to include e-mail and web browser. Contractors will be held accountable for actions they initiate on the network and will conduct business IAW USAF and local base instructions and policies. Sponsoring government agency will provide Information Assurance training prior to contractor access to network services. Contractor will require access to SIPRNET classified network for communication. Cleared contractor shall have access to classified information processing systems necessary to provide reporting information as identified in the Performance Work Statement (PWS).
Ref 11a. Have Access to Classified Information Only at another Contractor's Facility or Government Activity: Performance of the classified portion of this contract is restricted to facilities and/or the locations cited in item 8a, above. The COR will provide security classification guidance for performance of this contract. Collateral classified information may be processed, displayed, discussed or stored at the approved U.S. Government agency assigned. The highest level of security clearance required for contract performance is Secret. The government will oversee the handling and storage of classified information in support of this contract. The government will provide storage capability for all classified material required for this contract. Contractor personnel deployed to overseas locations may have access to classified information under the control of U.S. Military, Host Nation Military, or Embassy personnel. All classified information shall be returned to the U.S. Government upon termination of the contract.
Ref 11e. Perform services only: Contract is for assessment of networks/enclaves, training support and C&A products as stated in the PWS. Classification markings on the material to be furnished will provide the guidance necessary in performance of the contract.
ONSITE: All contractor personnel working onsite performing work under this contract shall possess at minimum a Secret clearance, based on a National Agency Check (NACLC) completed within the last 10 years (in-scope). The clearance must be fully adjudicated at the Secret level and will have an indication of “determined eligibility of Secret” in JPAS. Personnel security clearances (PCLs) must be verifiable in the Joint Personnel Adjudication System (JPAS) prior to reporting to any assignment within the installation assigned, in order to meet contractual security requirements. Foreign Nationals will not perform on any area of the contract (classified or unclassified). On the direction of the Contracting Officer's Representative, contractors may be required to support other PACAF bases as stated in the Performance Work Statement (PWS). Travel to other PACAF directed locations other than the assigned performance location will require a separate Visit Authorization Request (VAR) and a Letter of Identification (LOI) for official travel of government contractors.
Ref 11j Contractor will follow base and unit Operations Security guidance (SOPs, OIs, etc) for the locations identified in Item 8a. A copy of the local guidance will be provided to the contractor upon request.
-All U.S. contractors shall be provided annual program specific OPSEC training for all program personnel. These requirements, OPSEC Plan and training, shall be flowed down to all U.S. subcontractors with access to CUI and/or classified material.
- THREAT AWARENESS AND REPORTING REQUIREMENTS: IAW NISPOM 1-301, the contractor shall report threat-related incidents, behavioral indicators, and other matters of counterintelligence (CI) interest through the facility security officer to the government security officer, the nearest military AFOSI office, the Federal Bureau of Investigation, and the Defense Security Service. Annually, train personnel who handle classified information IAW AFI 16-1404. This requirement shall be flowed down to all U.S. subcontractors that have access to classified information/material.
Ref 12 Information requiring AF or DoD–level review will be forwarded by the entry-level public affairs office through the MAJCOM/DRU Public Affairs Office to the Secretary of the Air Force, Office of Public Affairs, Security and Review Division (SAF/PAX), 1690 Air Force Pentagon, Washington DC 20330-1690
Installation Information Protection (IP) Office Points of Contacts (POC):
15 WG/IP (JBPHH, HI): (added at contract award) 673 ABW/IP (JBER, AK): (added at contract award) 354 FW/IP (Eielson AFB, AK): (added at contract award) 36 WG/IP (Andersen AFB, GU & Diego Garcia, BIOT): (added at contract award) 51 FW/IP (Osan AB, ROK): (added at contract award) 8 FW/IP (Kunsan AB, ROK): (added at contract award) 18 WG/IP (Kadena AB, JP): (added at contract award) 374 AW/IP (Yokota AB, JP): (added at contract award) 35 FW/IP (Misawa AB, JP): (added at contract award)
| attachmentsList: |
| AddAttachment: |
| ViewAttachment: |
| RemoveAttachment: |
| rep: |
| Sig: |
| Enter your name here.: |
| GCAName: |
| AAC: |
| Address: |
| POCName: |
| Phone: |
| Email: |
| Title: |
| Enter the date using the format DD-Mon-YYYY: |
File details come from the government source that posted it.