<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE dita
  PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
<dita>
	  <concept id="GSAM_504_7005">
		    <title class="- topic/title ">
         <ph class="- topic/ph " props="autonumber">504.7005</ph> Notification procedures for cyber-supply chain events.</title>
		    <conbody>
			      <ol>
				        <li id="lXzEwI">
					          <p id="pRxQOl">
                  <ph props="autonumber" class="- topic/ph ">(a)</ph>
                  <i>General</i>. </p>
					          <ol>
						            <li id="gvis4m3">
							              <p id="8rh33ac">
                        <ph props="autonumber" class="- topic/ph ">(1)</ph> For any potential cyber-supply chain event, including occurrence of an IT security incident, discovery of a prohibited article or source, or identification of supply chain risk information, the contracting officer or another acquisition team member must contact the GSA IT Service Desk by phone at 866-450-5250 or by email at <xref format="html" href="mailto:ITServiceDesk@gsa.gov" scope="external">ITServiceDesk@gsa.gov</xref>. </p>
							              <ol>
								                <li id="gh97zv6">
									                  <p id="biwqrd8">
                              <ph props="autonumber" class="- topic/ph ">(i)</ph> Do not include source selection sensitive information in the notification to the GSA IT Service Desk. </p>
								                </li>
								                <li id="3kcnnrl">
									                  <p id="7kcf23ye8">
                              <ph props="autonumber" class="- topic/ph ">(ii)</ph> Do not include other sensitive information (e.g., IP address, access information such as an account login and password) in the notification to the GSA IT Service Desk. The notification should state that additional information is sensitive and will be provided in person or via a secured method. </p>
								                </li>
								                <li id="gjvoor90y">
									                  <p id="1mvybbs5">
                              <ph props="autonumber" class="- topic/ph ">(iii)</ph> Determining whether the identified issue or potential issue is applicable under the procedures for each event type should not delay the acquisition team member from submitting a notification. When unsure, it is better to notify quickly rather than delay the event notification. The GSA IT Service Desk can assist in defining the event type once submitted. </p>
								                </li>
							              </ol>
						            </li>
					          </ol>
				        </li>
				        <li id="ezi2nwhd">
					          <p id="i6ud4ayr">
                  <ph props="autonumber" class="- topic/ph ">(b)</ph>
                  <i>Occurrence of an IT security incident</i>. </p>
					          <ol>
						            <li id="c4fca4dn">
							              <p id="ag0n1r7t">
                        <ph props="autonumber" class="- topic/ph ">(1)</ph> If an IT security incident occurs, concerning any GSA information system or data (owned or operated by GSA or by a contractor or other organization on behalf of GSA), regardless of the estimated value of the contract or order, including purchases under the micro-purchase threshold and purchases using a Government Purchase Card, the contracting officer or another acquisition team member must immediately contact the GSA IT Service Desk. </p>
						            </li>
						            <li id="8qxlbv8f">
							              <p id="e6cuaxf">
                        <ph props="autonumber" class="- topic/ph ">(2)</ph> The notification to the GSA IT Service Desk - whether via phone or email - should document as much information as possible, including: </p>
							              <ol>
								                <li id="y2ledfqt">
									                  <p id="ch1qg1n">
                              <ph props="autonumber" class="- topic/ph ">(i)</ph> Description, date and time of the incident; </p>
								                </li>
								                <li id="z7xws2bk">
									                  <p id="h7zmja5h">
                              <ph props="autonumber" class="- topic/ph ">(ii)</ph> Whether any PII or contractor-attributional information is affected; and </p>
								                </li>
								                <li id="mr2egknmn">
									                  <p id="ssr9j72c">
                              <ph props="autonumber" class="- topic/ph ">(iii)</ph> Contract information (contract number, contractor name, name of GSA contracting office), as applicable. </p>
								                </li>
							              </ol>
						            </li>
						            <li id="4wy3wzm">
							              <p id="x7n1dyn7">
                        <ph props="autonumber" class="- topic/ph ">(3)</ph> Do not delay notifying the GSA IT Service Desk even if all the information requested or considered to be relevant is not available. </p>
						            </li>
						            <li id="69bs2qcp">
							              <p id="smxhqn7s">
                        <ph props="autonumber" class="- topic/ph ">(4)</ph> Additional guidance is available from the GSA IT Security Procedural Guide CIO-IT Security-01-02, “Incident Response (IR)”, and GSA IT Security Procedural Guide CIO-IT Security-21-117, “OCISO Cyber Supply Chain Risk Management (C-SCRM) Program”. </p>
						            </li>
						            <li id="kh0u5frv">
							              <p id="ltc8qbf">
                        <ph props="autonumber" class="- topic/ph ">(5)</ph> After initial notification, GSA IT may request additional information and will work with the notifier to resolve the issue. </p>
						            </li>
					          </ol>
				        </li>
				        <li id="maclxt9">
					          <p id="uzgzf59i">
                  <ph props="autonumber" class="- topic/ph ">(c)</ph>
                  <i> Discovery of a prohibited article or source </i>.</p>
					          <ol>
						            <li id="lWVNky">
							              <p id="zeFeMD">
                        <ph props="autonumber" class="- topic/ph ">(1)</ph>If a prohibited article or source is discovered within the supply chain of a procurement, regardless of the estimated value of the solicitation, contract, or order, including purchases under the micro-purchase threshold and purchases using a Government Purchase Card, the contracting officer or another acquisition team member must immediately contact the GSA IT Service Desk.</p>
						            </li>
						            <li id="zMDsAR">
							              <p id="WgiUWF">
                        <ph props="autonumber" class="- topic/ph ">(2)</ph>The notification to the GSA IT Service Desk - whether via phone or email - should document as much information as possible, including:</p>
							              <ol>
								                <li id="xhvsQL">
									                  <p id="EIGHkS">
                              <ph props="autonumber" class="- topic/ph ">(i)</ph>Contract or solicitation information, including contract or solicitation number, contractor or offeror name, and name of GSA contracting office;</p>
								                </li>
								                <li id="UKaEHp">
									                  <p id="qbUlDh">
                              <ph props="autonumber" class="- topic/ph ">(ii)</ph>Prohibited article or source name; and</p>
								                </li>
								                <li id="xeXCRc">
									                  <p id="igycct">
                              <ph props="autonumber" class="- topic/ph ">(iii)</ph>Reason why prohibited article or source is banned on contract.</p>
								                </li>
								                <li id="g6lielgg">
									                  <p id="zk95b0la">
                              <ph props="autonumber" class="- topic/ph ">(iv)</ph> A “critical date,” no less than three (3) business days in the future, for when a response from GSA’s Supply Chain Review Board is requested. </p>
								                </li>
							              </ol>
						            </li>
						            <li id="hx25k6l">
							              <p id="u555i39v">
                        <ph props="autonumber" class="- topic/ph ">(3)</ph> Do not delay notifying the GSA IT Service Desk even if all the information requested or considered to be relevant is not available. </p>
						            </li>
						            <li id="q7565gfl">
							              <p id="eogwebx9">
                        <ph props="autonumber" class="- topic/ph ">(4)</ph> After initial notification, GSA’s Supply Chain Review Board may request additional information and will work with the notifier to resolve the issue. </p>
							              <ol>
								                <li id="bp5o28l">
									                  <p id="qoau8u4">
                              <ph props="autonumber" class="- topic/ph ">(i)</ph> If the SCRM Review Board has not responded by the “critical date” required by <xref href="504.7005.dita#GSAM_504_7005" outputclass="fm:ParaNumOnly">504.7005</xref>(c)(2)(iv), the contracting officer may make a determination without the SCRM Review Board’s input, but should seek input and guidance from the appropriate Cyber-Supply Chain Risk Management Policy Advisor (see GSAM <xref href="504.7003.dita#GSAM_504_7003" outputclass="fm:ParaNumOnly">504.7003</xref>(a)) and review additional guidance available on the GSA Acquisition Portal (<xref format="html" href="http://insite.gsa.gov/cscrm" scope="external">http://insite.gsa.gov/cscrm</xref>) prior to making the determination. </p>
								                </li>
							              </ol>
						            </li>
					          </ol>
				        </li>
				        <li id="9fs4ulvd">
					          <p id="95tx4eaq">
                  <ph props="autonumber" class="- topic/ph ">(d)</ph>
                  <i>Identification of supply chain risk information</i>. </p>
					          <ol>
						            <li id="yo74liia">
							              <p id="544h2u8h">
                        <ph props="autonumber" class="- topic/ph ">(1)</ph>If substantial supply chain risk information is identified, or the contracting officer or another acquisition team member including the GSA Information Technology Office (GSA IT) (e.g., Chief Information Officer, Chief Information Security Officer) thinks supply chain risk information should be voluntarily shared with the FASC, the contracting officer or another acquisition team member must contact the GSA IT Service Desk. The GSA IT Service Desk will gather relevant information and share it with the appropriate Cyber-Supply Chain Risk Management Policy Advisor. </p>
							              <ol>
								                <li id="nisyc89j">
									                  <p id="odkjqk1i">
                              <ph props="autonumber" class="- topic/ph ">(i)</ph> Service-level policy may adopt additional procedures to provide acquisition team members with guidance prior to notifying the GSA IT Service Desk. </p>
								                </li>
							              </ol>
						            </li>
						            <li id="2ergpyts">
							              <p id="glxm1gu">
                        <ph props="autonumber" class="- topic/ph ">(2)</ph> After initial notification, the appropriate Cyber-Supply Chain Risk Management Policy Advisor may request additional information and will work with the notifier to resolve the issue. </p>
						            </li>
						            <li id="a7kpzkn">
							              <p id="0wh1kfya">
                        <ph props="autonumber" class="- topic/ph ">(3)</ph> The Cyber-Supply Chain Risk Management Policy Advisors will share information with the Office of Acquisition Policy within OGP. </p>
						            </li>
                  <li>
                     <p>
                        <ph props="autonumber" class="- topic/ph ">(4)</ph>OGP will share supply chain risk information with relevant GSA offices and personnel, as appropriate, and with the FASC when: </p>
                     <ol>
                        <li>
                           <p>
                              <ph props="autonumber" class="- topic/ph ">(i)</ph>The FASC requests information associated with a particular source, a covered article, or a covered procurement (as defined at 41 U.S.C. 4713(k));</p>
                        </li>
                        <li>
                           <p>
                              <ph props="autonumber" class="- topic/ph ">(ii)</ph> GSA determines that a substantial supply chain risk associated with a source, a covered article, or a covered procurement exists as described in 41 C.F.R. 201-1.101; or </p>
                        </li>
                        <li>
                           <p>
                              <ph props="autonumber" class="- topic/ph ">(iii)</ph> GSA identifies supply chain risk management information (including both C-SCRM and non-C-SCRM risks) associated with a source, a covered article, or a covered procurement action and deems such information relevant to share with the FASC.</p>
                        </li>
                     </ol>
                  </li>
					          </ol>
				        </li>
				        <li id="OzHwUS">
					          <p id="BrbFJL">
                  <ph props="autonumber" class="- topic/ph ">(e)</ph>
                  <i> Cyber-Supply Chain Event Risk Mitigation</i>. The contract administration procedures under <xref format="html"
                        href="https://www.acquisition.gov/content/part-49-termination-contracts"
                        scope="external">FAR part 49</xref> (<i>e.g.,</i> cure notice, termination for cause, past performance review) can be used as needed to address immediate or future supply chain event concerns. Additional guidance on contract administration procedures is available on the GSA Acquisition Portal (<xref format="html" href="http://insite.gsa.gov/scrm" scope="external">http://insite.gsa.gov/cscrm</xref>).</p>
				        </li>
				        <li id="MBMkZo">
					          <p id="Onhfoz">
                  <ph props="autonumber" class="- topic/ph ">(f)</ph>
                  <i>Past Performance Evaluation</i>. The contracting officer must report any contractor non-compliance with supply chain requirements within the “Other Areas” portion of any applicable past performance evaluation form.</p>
				        </li>
			      </ol>
		    </conbody>
	  </concept>
</dita>
