Amendment 003 - DOJ-05 and DOJ-02.pdf

AMENDMENT OF SOLICITATION/ MODIFICATION OF CONTRACT 1. CONTRACT ID CODE PAGE OF PAGES

1 21

2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicable)

Amendment #003 12/11/2024

6. ISSUED BY CODE 7. ADMINISTERED BY (If other than Item 6) CODE

UNICOR, FEDERAL PRISON INDUSTRIES, INC.

400 First St NW Washington, DC 20534

UNICOR, FEDERAL PRISON INDUSTRIES, INC.

400 First St NW Washington, DC 20534 Attn: Josh Hassler, Contract Specialist

8. NAME AND ADDRESS OF CONTRACTOR (No., street, country, State and Zip Code) (x) 9A. AMENDMENT OF SOLICITATION NO.

SV0161-24

X

9B. DATED (SEE ITEM 11)

11/04/2024

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE

FACILITY

CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENT OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and the date specified for receipt of Offers __ is extended___ is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods: (a) By completing items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment number. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(X) A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, Appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103 (b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF :

X D. OTHER (Specify type of modification and authority)

FAR 15.206 Amending the Solicitation.

E. IMPORTANT : Contractor ____is not __X__ is required to sign this document and return 1 copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

See attachment A.

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

Josh Hassler, Contract Specialist

15B. CONTRACTOR/OFFEROR

15C. DATE

SIGNED

16B. UNITED STATES OF AMERICA 16C. DATE SIGNED

_______________________________________ BY

Signature of the person authorized to sign) (Signature of contracting officer)

NSN 7540-01-152-8070

PREVIOUS EDITION UNUSABLE 30-105

STANDARD FORM 30 (REV. 10-

83) Prescribed by GSA

FAR(48 CFR) 53.243

Attachment A: 12/11/2024

Amendment #003 is to add clause DOJ-05 (Oct 2023) Security of Department Information and Systems

(reference pages 3-13) and DOJ-02 Contractor Privacy Requirements (JAN 2022)

All other terms and conditions will remain unchanged.

������� !������� �����"����� ������������������� ���� ����������������������� ��������� ����� ������#����$��� !��������������������� ����� ���� %�� &'()*+,-.)'/�������������������������0102������� � ������ ���������������������������3��� ���4���

��5������ ������� � ������ ���������������������������3���

K��������� ���������� ��3������ ��3��

�M����������� �������� ������ ��������� ������������ ����� ����M�����������

����������������������0102���

������������� ����������������������4

�� ������M���������������������������������������;��������� �����������������

�� ������M��������������������������������������;������������� ���@)-:'-.,A�7:â*.-8�b*:,ac�deWfWPONgXWfh�ijkXWOXPNT�lfWNmeno�pWNOV�NOY�VSVqWmXWQh������� ����������� ���� ����� �������������������������])'(.*+:B�7:â*.-8�b*:,ac�deWfWPONgXWfh�irkOgPfpWQ�lfWNmeno�pWNOV�NOY� ����������� ���� ����� ������������������������ s�� 7:â*.-8�&'a.B:'-��������� �� ����� ������������� �� ���

�t�������;�����������

���� !� "#$�%&&�'#()$)*�+,-#$.%/0#,�123/).34�0,�%**0/0#,�/#�%,2�#/5)$�%66&07%8&)�$)9:0$).),/34�%3�3)/�-#$/5�0,�;%$/�+4�/5)�'#,/$%7/#$�35%&&�7#.6&2�<0/5�/5)�3)7:$0/2�$)9:0$).),/3�#-�/5)�")*)$%&�+,-#$.%/0#,�1)7:$0/2�=#*)$,0>%/0#,�?@A�BC�DEFG�HIJKLM?NOP�QRSTU@V�?@A�BC�FWXGP�YZ[#()$,.),/� 7/�BC�DEEDP�\UASB]Û�K]_ASÀAa�BC�LAU]bURb_�U]b�ca@d]B̂BeV�HI\KLcNO�Lfa@SÛ�Q̀ĝS@UASB]_�HILQNOP�0,7&:*0,h�i+1j�1;�kllZmn4�kllZom4�%,*�kllZpl�q#&:.)3�+�%,*�++4�")*)$%&�+,-#$.%/0#,�;$#7)330,h�1/%,*%$b_�HIJKQLNO�Q̀ĝS@UASB]_�FGEZr4�stt4�%,*�rll4�")*)$%&�u03v�%,*� :/5#$0>%/0#,�=%,%h).),/�QRBeRUw�HIJabx?MQNOP�yz{�Kc�La@̀RSAV�LAU]bURb_�U_�Uwa]bab4�%,*�|=}�=).#$%,*%�$)&%/0,h�/#�/5)�3)7:$0/2�#-�0,-#$.%/0#,�%,*~#$�")*)$%&�+,-#$.%/0#,�123/).3!��}!� +,�%**0/0#,4�-#$�%&&�'#()$)*�+,-#$.%/0#,�123/).34�/5)�'#,/$%7/#$�35%&&�7#.6&2�<0/5�/5)�-#&&#<0,h�$)9:0$).),/34�<5075�%$)�&03/)*�5)$)�#,&2�/#�50h5&0h5/�7)$/%0,�36)70-07�%66&07%8&)�$)9:0$).),/3�-$#.�#,)�#-�/5)�3#:$7)3�0*),/0-0)*�0,�/5)�-0$3/�6%$%h$%65�#-�/503�1)7/0#,!��j503�03�,#/�%,�)�5%:3/0()�&03/�#-�%&&�3:75�$)9:0$).),/3�<0/5�<5075�/5)�'#,/$%7/#$�03�#8&0h%/)*�/#�7#.6&24�%,*�/5)�#.0330#,�#-�%�$)9:0$).),/�-$#.�/503�&03/�35#:&*�,#/�8)�7#,3/$:)*�%3�,)h%/0,h�/5)�.%/)$0%&0/2�#-�/5%/�$)9:0$).),/!��j5)3)�$)9:0$).),/3�%,*�/5#3)�0,�/5)�%:/5#$0/0)3�0,�/5)�6$0#$�6%$%h$%65�35#:&*�8)�$)%*�/#h)/5)$!��s!�� �0.0/0,h�%77)33�/#��|��+,-#$.%/0#,�%,*�'#()$)*�+,-#$.%/0#,�123/).3�/#�%:/5#$0>)*�:3)$3�%,*�/#�/$%,3%7/0#,3�%,*�-:,7/0#,3�/5%/�%:/5#$0>)*�:3)$3�%$)�6)$.0//)*�/#�)�)$703)!��r!� ;$#(0*0,h�3)7:$0/2�%<%$),)33�/$%0,0,h�%/�&)%3/�%,,:%&&2�/#�%&&�'#,/$%7/#$�).6&#2))3�%,*�7#,/$%7/#$3�0,(#&()*�<0/5�/5)�'#()$)*�'#,/$%7/!��1:75�/$%0,0,h�35%&&�0,7&:*)4�8:/�,#/�8)�&0.0/)*�/#4�$)7#h,0>0,h�%,*�$)6#$/0,h�6#/),/0%&�0,*07%/#$3�#-�0,30*)$�/5$)%/3�/#�:3)$3�%,*�.%,%h)$3�#-��|��+,-#$.%/0#,�%,*�'#()$)*�+,-#$.%/0#,�123/).3!��m!�� '$)%/0,h4�6$#/)7/0,h4�%,*�$)/%0,0,h4�0,�%77#$*%,7)�<0/5�%66&07%8&)�$)9:0$).),/3�8:/�0,�%,2�)(),/�%/�&)%3/�:,/0&�/5)�)�60$%/0#,�#-�/5)�7#,/$%7/4�'#()$)*�+,-#$.%/0#,�123/).�%:*0/�$)7#$*34�$)6#$/34�%,*�3:66#$/0,h�*#7:.),/%/0#,�/#�),%8&)�$)(0)<0,h4�.#,0/#$0,h4�%,%&23034�0,()3/0h%/0#,4�$)7#,3/$:7/0#,4�%,*�$)6#$/0,h�#-�:,&%<-:&4�:,%:/5#$0>)*4�#$�0,%66$#6$0%/)�%7/0(0/2�$)&%/)*�/#�3:75�'#()$)*�+,-#$.%/0#,�123/).3�%,*~#$��|��+,-#$.%/0#,!���!�� =%0,/%0,0,h�%:/5#$0>%/0#,3�/#�#6)$%/)�%,2�'#()$)*�+,-#$.%/0#,�123/).!��o!�� ;)$-#$.0,h�7#,/0,:#:3�.#,0/#$0,h�#,�%&&�'#()$)*�+,-#$.%/0#,�123/).34�/#�0,7&:*)�8:/�,#/�8)�&0.0/)*�/#4�7#&&)7/0,h4�$)(0)<0,h4�%,*�%,%&2>0,h�%66$#6$0%/)�&#h3�%,*�/0.)&2�0,()3/0h%/0,h�3)7:$0/2�%&)$/3�%,*�6#/),/0%&�3)7:$0/2�0,70*),/3!��p!�� �3/%8&0350,h�%,*�.%0,/%0,0,h�8%3)&0,)�7#,-0h:$%/0#,3�%,*�7:$$),/�0,(),/#$0)3�#-�'#()$)*�+,-#$.%/0#,�123/).34�0,7&:*0,h�5%$*<%$)4�3#-/<%$)4�-0$.<%$)4�%,*�*#7:.),/%/0#,4�/5$#:h5#:/�/5)�+,-#$.%/0#,�123/).��)()&#6.),/��0-)727&)4�%,*�)3/%8&0350,h�%,*�),-#$70,h�3)7:$0/2�7#,-0h:$%/0#,�3)//0,h3�-#$�+j�6$#*:7/3�).6&#2)*�0,�'#()$)*�+,-#$.%/0#,�123/).3!��n!�� �,3:$0,h�%66$#6$0%/)�7#,/0,h),72�6&%,,0,h�5%3�8)),�6)$-#$.)*4�0,7&:*0,h��|��+,-#$.%/0#,�%,*�'#()$)*�+,-#$.%/0#,�123/).�8%7v:63!��k!�� +*),/0-20,h�'#()$)*�+,-#$.%/0#,�123/).�:3)$34�6$#7)33)3�%7/0,h�#,�8)5%&-�#-�:3)$34�#$�*)(07)34�%,*�%:/5),/07%/0,h�%,*�()$0-20,h�/5)�0*),/0/0)3�#-�3:75�:3)$34�6$#7)33)34�#$�*)(07)34�:30,h�.:&/0-%7/#$�%:/5),/07%/0#,�#$��1;�Zsr�7#.6&0%,/�%:/5),/07%/0#,�.)/5#*3�%3�*)-0,)*�82�i+1j�kllZpmZm4�����������������������������#$�7:$$),/�$)(030#,!��t!�� �3/%8&0350,h�%,*�.%0,/%0,0,h�%,�#6)$%/0#,%&�0,70*),/�5%,*&0,h�7%6%80&0/2�-#$�'#()$)*�+,-#$.%/0#,�123/).3�/5%/�0,7&:*)3�%*)9:%/)�%,*�/0.)&2�*)()&#6.),/4�&#hh0,h4�*)/)7/0#,4�%,%&23034�7#,/%0,.),/4�$)7#()$24�%,*�:3)$�$)36#,3)�%7/0(0/0)34�%,*�/$%7v0,h4�*#7:.),/0,h4�%,*�/0.)&2�$)6#$/0,h�0,70*),/3�/#�%66$#6$0%/)�#--070%&3�%,*�%:/5#$0/0)3�<0/50,�/5)��B]ARU@ABR�_�BReU]S�UASB]�U]b�Ada��|�!��

������/�� 0 �1 ��2�� ������0������ ��3412056�� �7 ����8�������������(����

�����3�

��������6�����9�� � ������32:;��%�%%.<�*6�����

��� !����������3��� � ���������6����

��������=>?@ABC@>ADE�� �

���34� 56��� ��1 ��F��� �����341F,56��

��������=>?@ABC@>ADE�� �

G������

�7

���������H��F����/��<'.�;�����

�%I�J@KL�M�NO=>?@P?Q>QE�R>?P@>AP?S5T�

��H��F�������

��%%�� U��

���E�LBA@�>V�>LKAB@P?S�WP@XP?�@XK�YZ[�K?\PA>?]K?@I�@XK�=>?@ABC@>ADE��

�������������$G�����

���./012341/256��������������������������������+��,� ����������7*�������������������������� ����*���7*�����""�(���������(�� ���7 ��+8����"� ����9��(�"���,������ *������

����������/?�@06AB41/2�CB0B23D�EFG@CHI�30J�KBJB23D�D3L�B0?/24BMB01���������

���./012341/256�?34NDN1NB6O����

���������8��#7��� ����P ��� ��7��� ���./012341/2�6Q3DD�4//AB231B�LN1Q�RGS56�B??/216�1/�B06T2BO�M3N013N0O�30J�63?BUT32J�1QB���� ������� 8�� *���

���8���������< ��"������������7������� �������)��*�8�;��&-:% �������������� ��������V�� ���W �������W ����X:����������W ������7""������������ ���������Y�� 7�� �(����������������V���"��������� �������������������("���W���

�������0�� 1������������

���2!����*�344�55"�6789:;8<:=�>?@�A:98B�CB<8D8EBD8?<����!�� ��������

��F4������� ������.�

��F4�� � ������G�� (#-"����

��"������ ����������HIJKLMNKILOP�MNNQPP�KI�MJR�STU�VJWILXMKYIJZ��

�����&������� ���� �K]Q�HIJKLMNKILOP�P̂P_QNKQ̀�WMYâLQ�KI�NIX_aR�bYK]�MJR�PQN̂LYKR�

���"��������HIJKLMNKILOP�Qc_QJPQd��������� ���e�$�fg�gg��Fh��$ ��(����"�e�$�fg�ghf�F��+��� ���"�(#-�gh44�i�������� �F������������� ���"�����e�$�h�54h�f��������* ���������jk�� lmnop�lnqrostuv����� ��������

�wx��*yz� �����'����

��+!,�0������ ���������� !)���-��1��� 0��������� ������2����

��+!,�!�0!-�����

2���� �����2��������� ���������3&��'�(����

��������+!,�0������

���5��

����+!,�0������ ����-��� �6�� �-������

��������������������������� ����O�� ����**���� �2�(�������� ����'(�����

��O!��5/1������P0� �����//6�Q�-�RSTUVWUXYVZ[S�\Y]]̂S�R_̀Za�bZWc�d̀ àeUfUa[�gV̀X[ZXUW�hiV�\SW[UfW�̀aj�kVèaZl̀[ZiaW-������*�����

��6� ������ ���-��������&0��6�mm�n

������+!,�0������

�2�(�������� ����

���C8GE7BGCE@A�*����� ���������

���������������� ooooo�

+�0,12�3��-�� ����4++��� +�5 �4����+�.��6+���-�780*�03�9::;)<)=�>��+-��?�@��* +�0,12����-��

�����4��+4+-���

+��+IB��+���+.B�����. -�� ������� .B4+-�+���-��

+�0,12�3��-���*

+��+IB��+4+-��� 5��

+�0,12����-�� ����5�

B�� 5����. /+��L��+� ����-��, -5��4+��0+.B�����8-.��+-��� ��

+�TJU�,J��-��,J1��85��

+�TJU�,J�- ���

+�,J1�.�-�6+��+�.

+�, -���.� ��4B���.����U0J,����);F:F;DCH;H:::��44+����+���K�-���-�- �+/+-�����+���

�-�FG�

L� +�3 �+-�����0+.B�����8-.��+-�� ����-�5�.����0+.B�����8-.��+-�=��

+�TJU�,J��-���

+�,J1���85�� +���4+�6��

+�TJU�,J�- ���

+�,J1�.�-�6+��+�.

����0�������1�

�%"$��1

���$���$2������%"$���� ���� ��������#�� 34�

�5���� �1

��$2�67�89:;<�=><?@A7>BCD���3�� 1�

�FBC7@6?7B@;<�AGHAC<AI�6�JKL9�6??AH76MNA�7B�89:I�O>7P�AGHA@7><A�>C�>C?>=AC7�

������/�� 2

�� �E��

���1�

�������QRRS�TUVVWXYZ[\]Y�[̂�_̀a\Zbcd�èf\bZ̀g̀ hcV�c[�_\ia[hcZUac[ZV�Uhj�k_TV����� 1�

DOJ-02 Contractor Privacy Requirements (JAN 2022)

A. Limiting Access to Privacy Act and Other Sensitive Information

(1) Privacy Act Information

In accordance with FAR 52.224-1 Privacy Act Notification (APR 1984) and FAR 52.224-2

Privacy Act (APR 1984), if this contract requires Contractor personnel to have access to information protected by the Privacy Act of 1974, the contractor is advised that the relevant DOJ system of records notices (SORN s) applicable to this Privacy Act information may be found at https://www.justice.gov/opcl/doj-systems-records. [l] Applicable SORNs published by other agencies may be accessed through those agencies' websites or by searching the Federal Digital

System (FDsys) available at http://www.gpo.gov/fdsys/. SORNs may be updated at any time.

(2) Prohibition on Performing Work Outside a Government Facility/Network/Equipment

Except where use of Contractor networks, IT, other equipment, or Workplace as a Service

(WaaS) is specifically authorized within this contract, the Contractor shall perform all tasks on authorized Government networks, using Government-furnished IT and other equipment and/or

WaaS and Government information shall remain within the confines of authorized Government networks at all times. Any handling of Government information on Contractor networks or IT must be approved by the Senior Component Official for Privacy of the component entering into this contract. Except where remote work is specifically authorized within this contract, the

Contractor shall perform all tasks described in this document at authorized Government facilities; the Contractor is prohibited from performing these tasks at or removing Government-furnished information to any other facility; and Government information shall remain within the confines of authorized Government facilities at all times. Contractors may only access classified materials on government furnished equipment in authorized government owned facilities regardless of remote work authorizations.

(3) Prior Approval Required to Hire Subcontractors

The Contractor is required to obtain the Contracting Officer's approval prior to engaging in any contractual relationship (Subcontractor) in support of this contract requiring the disclosure of information, documentary material and/or records generated under or relating to this contract.

The Contractor (and any Subcontractor) is required to abide by Government and Agency guidance for protecting sensitive and proprietary information.

(4) Separation Checklist for Contractor Employees

The Contractor shall complete and submit an appropriate separation checklist to the Contracting

Officer before any employee or Subcontractor employee terminates working on the contract. The

Contractor must submit the separation checklist on or before the last day of employment or work on the contract. The separation checklist must verify: ( 1) return of any Government-furnished equipment; (2) return or proper disposition of personally identifiable information (PI1) [2], in paper or electronic form, in the custody of the employee or Subcontractor employee including the sanitization of data on any computer systems or media as appropriate; and (3) termination of any technological access to the Contractor's facilities or systems that would permit the terminated employee's access to PII or other sensitive information.

In the event of adverse job actions resulting in the dismissal of a Contractor or Subcontractor employee before the separation checklist can be completed, the Prime Contractor must notify the

Contracting Officer within 24 hours and confirm receipt of the notification. In the case the

Contractor is unable to notify the Contracting Officer, then the Contractor should notify the

Contract Officer's Representative (COR).

Contractors must complete the separation checklist with the Contracting Officer or COR by returning all Government-furnished property including, but not limited to, computer equipment, media, credentials and passports, smart cards, mobile devices, Personal Identity Verification

(PIV) cards, calling cards, and keys and terminating access to all user accounts and systems.

Unless the Contracting Officer requests otherwise, the relevant Program Manager or other Key

Personnel designated by the Contracting Officer or COR may facilitate the return of equipment.

B. Privacy Training, Safeguarding, and Remediation

(1) Required Security and Privacy Training for Contractors

The Contractor must ensure that all employees take appropriate privacy training, including

Subcontractors who have access to PII as well as the creation, use, dissemination and/or destruction of PII at the outset of the employee's work on the contract and every year thereafter.

Training must include procedures on how to properly handle PII, including heightened security requirements for the transporting or transmission of sensitive PII, and reporting requirements for a suspected breach or loss of PII. These courses, along with more information about DOJ security and training requirements for Contractors, are available at https://www.justice.gov/jmd/learndoj. The Federal Information Security Modernization Act of2014 (FISMA) requires all individuals accessing DOJ information to complete training on records management, cybersecurity awareness, and information system privacy awareness.

Contractor employees are required to sign the "Privacy Rules of Behavior," acknowledging and agreeing to abide by privacy law, policy, and certain privacy safeguards, prior to accessing DOJ information. These Rules of Behavior are made available to all new users of DOJ's computer network and to trainees at the conclusion of DOJ-OPCL-CS-0005.

The Contractor should maintain copies of certificates as a record of compliance and must submit an email notification annually to the COR verifying that all employees working under this contract have completed the required privacy and cybersecurity training.

(2) Safeguarding PII Requirements

Contractor employees must comply with DOJ Order 0904 and other guidance published to the publicly-available Office of Privacy and Civil Liberties (OPCL) Resources page[3] relating to the safeguarding of PII, including the use of additional controls to safeguard sensitive PII ( e.g., the encryption of sensitive PII). This requirement flows down from the Prime Contractor to all

Subcontractors and lower tiered subcontracts.

(3) Non-Disclosure Agreement Requirement

Prior to commencing work, all Contractor personnel that may have access to PII or other sensitive information shall be required to sign a Non-Disclosure Agreement (NDA) and the DOJ

IT Rules of Behavior. The Non-Disclosure Agreement:

(a) prohibits the Contractor from retaining or divulging any PII or other sensitive information, or derivatives therefrom, furnished by the Government or to which they may otherwise come in contact as a result of their performance of work under the contract/task order that is otherwise not publicly available, whether or not such information has been reduced to writing; and

b) requires the Contractor to report any loss of control, compromise, unauthorized disclosure, or unauthorized acquisition of PII or other sensitive information to the component-level or headquarters Security Operations Center within one (1) hour of discovery.

The Contractor should maintain signed copies of the NDA for all employees as a record of compliance. The Contractor should also provide copies of each employee's signed NDA to the

Contracting Officer before the employee may commence work under the contract/task order.

( 4) Prohibition on Use of PII in Vendor Billing and Administrative Records

The Contractor's invoicing, billing, and other financial or administrative records or databases is not authorized to regularly store or include any sensitive PII or other confidential government information that is created, obtained, or provided during the performance of the contract without the written permission of the Senior Component Official for Privacy (SCOP). It is acceptable to list the names, titles and contact information for the Contracting Officer, COR, or other personnel associated with the administration of the contract in the invoices as needed.

(5) Reporting Actual or Suspected Data Breach

Contractors must report any actual or suspected breach of PII within one hour of discovery. [ 4]

A "breach" is an incident or occurrence that involves the loss of control, compromise, unauthorized disclosure, unauthorized acquisition, or any similar occurrence where: (1) a person other than an authorized user accesses or potentially accesses PII or (2) an authorized user accesses or potentially accesses PII for an other than authorized purpose. The report of a breach must be made to DOJ. The Contractor must cooperate with DOJ's inquiry into the incident and efforts to minimize risks to DOJ or individuals, including remediating any harm to potential victims.

(a) The Contractor must develop and maintain an internal process by which its employees and Subcontractors are trained to identify and report the breach, consistent with DOJ Instruction

0900.00.01 [5], Reporting and Response Procedures for a Breach of Personally Identifiable

Information.

(b) The Contractor must report any such breach by its employees or Subcontractors to the

DOJ Security Operations Center (dojcert@usdoj.gov, 202-357-7000); Component-level Security

Operations Center and Component-level Management Team, where appropriate; the COR; and the Contracting Officer within one (1) hour of the initial discovery.

(c) The Contractor must provide a written report to the DOJ Security Operations Center

(dojcert@usdoj.gov, 202-357-7000) within 24 hours of discovery of the breach by its employees or Subcontractors. The report must contain the following information:

(i) Narrative or detailed description of the events surrounding the suspected loss or compromise of information.[6] Date, time, and location of the incident.

(ii) Amount, type, and sensitivity of information that may have been lost or compromised, accessed without authorization, etc.

(iii) Contractor's assessment of the likelihood that the information was compromised or lost and the reasons behind the assessment. [7]

(iv) Names and classification of person(s) involved, including victim, Contractor employee/Subcontractor and any witnesses.

(v) Cause of the incident and whether the company's security plan was followed and, if not, which specific provisions were not followed.[8]

(vi) Actions that have been or will be taken to minimize damage and/or mitigate further compromise.

(vii) Recommendations to prevent similar situations in the future, including whether the security plan needs to be modified in any way and whether additional training may be required.

(d) The Contractor shall provide full access and cooperation for all activities determined by the Government to be required to ensure an effective incident response, including providing all requested images, log files, and event information to facilitate rapid resolution of sensitive information incidents.

(e) At the Government's discretion, Contractor employees or Subcontractor employees may be identified as no longer eligible to access PII or to work on that contract based on their actions related to the loss or compromise of PII.

(6) Victim Remediation

At DOJ's request, the Contractor is responsible for notifying victims and providing victim remediation services in the event of a breach of PII held by the Contractor, its agents, or its

Subcontractors, under this contract. Victim remediation services shall include at least 18 months of credit monitoring and, for serious or large incidents as determined by the Government, call center help desk services for the individuals whose PII was lost or compromised. When DOJ requests notification, the Department Chief Privacy and Civil Liberties Officer and SCOP will direct the Contractor on the method and content of such notification to be sent to individuals whose PII was breached. By performing this work, the Contractor agrees to full cooperation in the event of a breach. The Contractor should be self-insured to the extent necessary to handle any reasonably foreseeable breach, with another source of income, to fully cover the costs of breach response, including but not limited to victim remediation.

C) Government Records Training, Ownership, and Management

(1) Records Management Training and Compliance

(a) The Contractor must ensure that all employees and Subcontractors that have access to PII as well as to those involved in the creation, use, dissemination and/or destruction of PII take the

DOJ Records and Information Training for New Employees (RIM) training course or another training approved by the Contracting Officer or COR. This training will be provided at the outset of the Subcontractor's/employee's work on the contract and every year thereafter. The

Contractor shall maintain copies of certificates as a record of compliance and must submit an email notification annually to the COR verifying that all employees working under this contract have completed the required records management training.

(b) The Contractor agrees to comply with Federal and Agency records management policies, including those policies associated with the safeguarding of records containing PII and those covered by the Privacy Act of 1974. These policies include the preservation of all records created or received regardless of format, mode of transmission, or state of completion.

(2) Records Creation, Ownership, and Disposition

(a) The Contractor shall not create or maintain any records not specifically tied to or authorized by the contract using Government IT equipment and/or Government records or that contain Government Agency information. The Contractor shall certify, in writing, the appropriate disposition or return of all Government information at the conclusion of the contract or at a time otherwise specified in the contract. In accordance with 36 CFR 1222.32, the

Contractor shall maintain and manage all Federal records created in the course of performing the contract in accordance with Federal law. Records may not be removed from the legal custody of

DOJ or destroyed except in accordance with the provisions of the agency records schedules.

(b) Except as stated in the Performance Work Statement and, where applicable, the

Contractor's Commercial License Agreement, the Government Agency owns the rights to all electronic information (electronic data, electronic information systems or electronic databases and all supporting documentation and associated metadata created as part of this contract. All deliverables (including all data and records) under the contract are the property of the U.S.

Government and may be considered federal records, for which the Agency shall have unlimited rights to use, dispose of, or disclose such data contained therein. The Contractor must deliver sufficient technical documentation with all data deliverables to permit the agency to use the data.

(c) The Contractor shall not retain, use, sell, disseminate, or dispose of any government data/records or deliverables without the express written permission of the Contracting Officer or

Contracting Officer's Representative. The Agency and its contractors are responsible for preventing the alienation or unauthorized destruction of records, including all forms of mutilation. Willful and unlawful destruction, damage or alienation of Federal records is subject to the fines and penalties imposed by 18 U.S.C. § 2701. Records may not be removed from the legal custody of the Agency or destroyed without regard to the provisions of the Agency records schedules.

D. Data Privacy and Oversight

(1) Restrictions on Testing or Training Using Real Data Containing PII

The use of real data containing PII from any source for testing or training purposes is generally prohibited. The Contractor shall use synthetic or de-identified real data for testing or training whenever feasible.

(2) Requirements for Contractor IT Systems Hosting Government Data

The Contractor is required to obtain an Authority To Operate (ATO) for any IT environment owned or controlled by the Contractor or any Subcontractor on which Government data shall reside for the purposes of IT system development, design, data migration, testing, training, maintenance, use, or disposal.

(3) Requirement to Support Privacy Compliance

(a) If this contract requires the development, maintenance or administration of information technology[9], the Contractor shall support the completion of the Initial Privacy Assessment

(IPA) document, if requested by Department personnel. An IP A is the first step in a process to identify potential privacy issues and mitigate privacy risks. The IP A asks basic questions to help components assess whether additional privacy protections may be needed in designing or implementing a project[lO] to mitigate privacy risks, and whether compliance work may be needed. Upon review of the IPA, the OPCL determines whether a Privacy Impact Assessment

(PIA) document and/or SORN, or modifications thereto, are required. The Contractor shall provide adequate support to complete the applicable risk assessment and PIA document in a timely manner, and shall ensure that project management plans and schedules include the IPA, PIA, and SORN (to the extent required) as milestones. Additional information on the privacy compliance process at DOJ, including IP As, PIAs, and SORNs, is located on the DOJ OPCL website (https://dojnet.doj.gov/privacy/), including DOJ Order 0601, Privacy and Civil Liberties.

The Privacy Impact Assessment Guidance and Template outline the requirements and format for the PIA.

(b) If the contract involves an IT system build or substantial development or changes to an IT system that may require privacy risk assessment and documentation, the Contractor shall provide adequate support to DOJ to ensure DOJ can complete any required assessment, and IPA, PIA, SORN, or other supporting documentation to support privacy compliance. The Contractor shall work with personnel from the program office, OPCL, the Office of the Chief lnformation Officer

(OCIO), and the Office of Records Management and Policy to ensure that the privacy assessments and documentation are kept on schedule, that the answers to questions in the documents are thorough and complete, and that questions asked by the OPCL and other offices are answered in a timely fashion. The Contractor must ensure the completion of required PIAs and documentation of privacy controls consistent with federal law and standards, e.g. NIST 800-

53, Rev. 5; and compliance with the Privacy Act of 1974, E-Government Act of 2002, Federal

Information Security Modernization Act of 2014, and key 0MB guidelines, e.g., 0MB Circular

A-130.

[1] "[T]he term 'record' means any item, collection, or grouping of information about an individual that is maintained by an agency, including, but not limited to, his education, financial transactions, medical history, and criminal or employment history and that contains his name, or the identifying number, symbol, or other identifying particular assigned to the individual, such as a finger or voice print or a photograph." 5 U.S.C. § 552a(a)( 4). "[T]he term 'system of records' means a group of any records under the control of any agency from which information is retrieved by the name of the individual or by some identifying number, symbol, or other identifying particular assigned to the individual." 5 U.S.C. § 552a(a)(5).

[2] As stated in FAR 52.224-3 and Office of Management and Budget (0MB) Circular A-

130, Managing Federal Information as a Strategic Resource (2016), "'personally identifiable information' means information that can be used to distinguish or trace an individual's identity, either alone or when combined with other information that is linked or linkable to a specific individual." Regarding "sensitive PII," "[t]he sensitivity level of the PII will depend on the context, including the purpose for which the PII is created, collected, used, processed, stored, maintained, disseminated, disclosed, or disposed. For example, the sensitivity level of a list of individuals' names may depend on the source of the information, the other information associated with the list, the intended use of the information, the ways in which the information will be processed and shared, and the ability to access the information." 0MB Circular A-130, at

App. 11-2.

[3] The DOJ OPCL Resources page is available at https://www.justice.gov/opcl/resources.

[4] As stated in DOJ Instruction 0900, "Contractors must notify the Contracting Officer, the

Contracting Officer's Representative, and JSOC (or component-level SOC) within 1 hour of discovering any incidents, including breaches, consistent with this Instruction, guidance issued by the CPCLO, NIST standards and guidelines, and the US-CERT notification guidelines."

[ 5] https://www .justice.gov/file/4336/download

[ 6] As stated in DOJ Instruction 0900, the description should include the type of information that constitutes PII; purpose for which PII is collected, maintained, and used; extent to which PII identifies a peculiarly vulnerable population; the determination of whether the information was properly encrypted or rendered partially or completely inaccessible by other means; format of PII

(e.g., whether PII was structured or unstructured); length of time PII was exposed; any evidence confirming that PII is being misused or that it was never accessed.

[7] As stated in DOJ Instruction 0900, the report should include the nature of the cyber threat

(e.g., Advanced Persistent Threat, Zero Day Threat, data exfiltration) for cyber incidents.

[8] As stated in DOJ Instruction 0900, the report should include analysis on whether the data is accessible, usable, and intentionally targeted.

[9] As defined in 40 U.S.C. § 11101, the term "information technology" means any equipment or interconnected system or subsystem of equipment, used in the automatic acquisition, storage, analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information by the executive agency, if the equipment is used by the executive agency directly or is used by a contractor under a contract with the executive agency that requires the use (i) of that equipment or (ii) of that equipment to a significant extent in the performance of a service or the furnishing of a product; includes computers, ancillary equipment (including imaging peripherals, input, output, and storage devices necessary for security and surveillance), peripheral equipment designed to be controlled by the central processing unit of a computer, software, firmware and similar procedures, services (including support services), and related resources; but does not include any equipment acquired by a federal contractor incidental to a federal contract.

[10] In this instance, the term "project" is used to scope the activities (e.g., creating, collecting, using, processing, storing, maintaining, disseminating, disclosing, or disposing of information) covered by an IPA. A project is intended to be technology-neutral, and may include an information system, a digital service, an information technology, a combination thereof, or some other activity that may create potential privacy issues or privacy risks that would benefit from an

IP A. The scope of a project covered by an IPA is discretionary, but components should work with their SCOP and OPCL.

(End of Clause)