Exhibit_A_CDRLs_&_DIDs.pdf

PDF 426 KB Posted Sep 12, 2017

Attached to: IA Support Services Federal contract opportunity
Solicitation number: N6426717T0310
Issued by: Department of the Navy Naval Sea Systems Command

About this file

From the source

Exhibit A CDRLs & DIDs

View the file

Other files for this federal contract opportunity

Other files attached to IA Support Services, newest first.
File	Type	Posted
Q&A_Rev1.docx	DOCX document	Sep 14, 2017
Q&A.docx	DOCX document	Sep 12, 2017
RFQ_N6426717T0310.pdf	PDF	Sep 12, 2017
Attachment_1_Applicable_Directives.pdf	PDF	Sep 12, 2017
Attachment_2_WD_No._2015-5629_Rev5.pdf	PDF	Sep 12, 2017

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

DD FORM 1423-1, FEB 2001

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours 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, Executive Services and Communications Directorate (0704-0188). 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. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

MGMT

DATA MANAGEMENT SERVICES TBD

A001 CONTRACTOR'S PROGRESS STATUS AND

MANAGEMENT REPORT

MONTHLY STATUS REPORT

DI-MGMT-80227 SOW PARA 6.0 NSWC CORONA (AR30)

N/A C

MTHLY

N/A

30DAC/See Blk 16

SEE BLK 16

J. Trunko (AR30) 1

0 1 0

BLK 4 – CONTRACTOR FORMAT IS ACCEPTABLE.

BLK 9 - USE THE FOLLOWING: "DISTRIBUTION STATEMENT C.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND

THEIR CONTRACTORS ONLY. (REASON: ADMINISTRATIVE USE).

OTHER REQUESTS FOR THIS DOCUMENT SHALL BE REFERRED TO

NAVAL SURFACE WARFARE CENTER, CORONA DIVISION, CORONA

CA."

BLK 12 - THE REPORTING PERIOD SHALL BE FROM THE FIRST TO LAST

BUSINESS DAY OF EACH MONTH, BEGINNING WITHIN 30 CALENDAR

DAYS AFTER EFFECTIVE DATE OF ORDER.

BLK 13 - SUBSEQUENT REPORTS SUBMITTED MONTHLY THEREAFTER,

NOT LATER THAN THE 10TH DAY OF THE REPORTING MONTH.

BLK 14 - ELECTRONIC COPY SHALL BE BY E-MAIL IN MICROSOFT

OFFICE COMPATIBLE OR PDF FORMAT IN ACCORDANCE WITH CDRL

DISTRIBUTION BLOCK 14.

ADDRESSEE(S) EMAIL ADDRESS: joseph.trunko@navy.mil

19 July 2017

BERGLAND.KA

RI.L.1263458067

Digitally signed by

BERGLAND.KARI.L.1263458067

Date: 2017.08.15 13:10:02 -07'00' 15 August 2017

1 1

TRUNKO.JOSEPH.M

ICHAEL.1228939990

Digitally signed by

TRUNKO.JOSEPH.MICHAEL.1228

939990 Date: 2017.07.19 10:02:27 -07'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

MGMT

DATA MANAGEMENT SERVICES TBD

A002 DOD INFORMATION ASSURANCE

CERTIFICATION AND ACCREDITATION PROCESS

RMF DOCUMENTATION

DI-MGMT-82000 SOW PARA 5.1 AND 6.0 NSWC CORONA (AR30)

N/A C

ASREQ (See Blk 16)

N/A

ASREQ (See Blk 16)

ASREQ (See Blk 16) J. Trunko (AR30) 1

0 1 0

BLK 4/5 - (DI-MGMT-82000) PARAGRAPH 2.1.6, 2.1.8 AND 2.1.9 DO NOT

APPLY AND SHOULD BE TAILORED OUT FROM THE DELIVERABLE.

SOW PARAGRAPH 5.1 IS MANDATORY TO THIS REQUIREMENT.

BLK 9 - USE THE FOLLOWING: "DISTRIBUTION STATEMENT C.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND

THEIR CONTRACTORS ONLY. (REASON: ADMINISTRATIVE USE).

OTHER REQUESTS FOR THIS DOCUMENT SHALL BE REFERRED TO

NAVAL SURFACE WARFARE CENTER, CORONA DIVISION, CORONA

CA."

BLK 10, 12, 13 – DOCUMENTATION DUE IN ACCORDANCE WITH C&A

PLAN FOR INITIAL ACCREDITATION AND FIVE (5) DAYS AFTER EACH

REVIEW OR REQUIRED CHANGE.

BLK 14 - ELECTRONIC COPY SHALL IN ODAA REQUIRED COMPATIBLE

FILE FORMAT SUBMITTED PER ODAA DIRECTIVES (eMASS) AND BY

E-MAIL IN MICROSOFT OFFICE / PDF FORMAT IN ACCORDANCE WITH

CDRL DISTRIBUTION BLOCK 14.

ADDRESSEE(S) EMAIL ADDRESS: joseph.trunko@navy.mil

19 July 2017

BERGLAND.KA

RI.L.1263458067

Digitally signed by

BERGLAND.KARI.L.1263458067

Date: 2017.08.15 14:30:56 -07'00' 15 August 2017

1 1

TRUNKO.JOSEPH.M

ICHAEL.1228939990

Digitally signed by

TRUNKO.JOSEPH.MICHAEL.1228

Date: 2017.07.19 10:02:27 -07'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

MGMT

DATA MANAGEMENT SERVICES TBD

A003 DOD INFORMATION ASSURANCE

CERTIFICATION AND ACCREDITATION PROCESS

SCAN RESULTS

DI-MGMT-82000 SOW PARA 5.1 AND 6.0 NSWC CORONA (AR30)

N/A C

ASREQ (See Blk 16)

N/A

ASREQ (See Blk 16)

ASREQ (See Blk 16) J. Trunko (AR30) 1

0 1 0

BLK 4 - (DI-MGMT-82000) ONLY PARAGRAPHS 1, 2, 2.1, 2.1.12, AND 2.1.13

ARE APPLICABLE. OTHER PARAGRAPHS OF THIS DID ARE NOT

REQUIRED AND SHOULD BE TAILORED OUT. SOW PARAGRAPH 5.1 IS

MANDATORY TO THIS REQUIREMENT.

BLK 9 - USE THE FOLLOWING: "DISTRIBUTION STATEMENT C.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND

THEIR CONTRACTORS ONLY. (REASON: ADMINISTRATIVE USE).

OTHER REQUESTS FOR THIS DOCUMENT SHALL BE REFERRED TO

NAVAL SURFACE WARFARE CENTER, CORONA DIVISION, CORONA

CA."

BLK 10, 12, 13 – SCAN RESULTS ARE DUE WITHIN 7 DAYS OF EACH

SYSTEM’S VALIDATION.

BLK 14 - ELECTRONIC COPY SHALL IN ODAA REQUIRED COMPATIBLE

FILE FORMAT SUBMITTED PER ODAA DIRECTIVES (eMASS) AND BY

E-MAIL IN MICROSOFT OFFICE / PDF FORMAT IN ACCORDANCE WITH

CDRL DISTRIBUTION BLOCK 14.

ADDRESSEE(S) EMAIL ADDRESS: joseph.trunko@navy.mil

19 July 2017

BERGLAND.KA

RI.L.1263458067

Digitally signed by

BERGLAND.KARI.L.1263458067

Date: 2017.08.15 14:25:29 -07'00' 15 August 2017

1 1

TRUNKO.JOSEPH.M

ICHAEL.1228939990

Digitally signed by

TRUNKO.JOSEPH.MICHAEL.1228

Date: 2017.07.19 10:04:15 -07'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

MGMT

DATA MANAGEMENT SERVICES TBD

A004 DOD INFORMATION ASSURANCE

CERTIFICATION AND ACCREDITATION PROCESS

ANNUAL SECURITY REVIEW AND

ANNUAL TESTING OF SECURITY

DI-MGMT-82000 SOW PARA 5.2 AND 6.0 NSWC CORONA (AR30)

N/A C

ASREQ (See Blk 16)

N/A

ASREQ (See Blk 16)

ASREQ (See Blk 16) J. Trunko (AR30) 1

0 1 0

BLK 4/5 - (DI-MGMT-82000) PARAGRAPH 2.1.6, 2.1.8 AND 2.1.9 DO NOT

APPLY AND SHOULD BE TAILORED OUT FROM THE DELIVERABLE.

SOW PARAGRAPH 5.2 IS MADATORY TO THIS REQUIREMENT.

BLK 9 - USE THE FOLLOWING: "DISTRIBUTION STATEMENT C.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND

THEIR CONTRACTORS ONLY. (REASON: ADMINISTRATIVE USE).

OTHER REQUESTS FOR THIS DOCUMENT SHALL BE REFERRED TO

NAVAL SURFACE WARFARE CENTER, CORONA DIVISION,

CORONA CA."

BLK 10, 12, 13 – ANNUAL REVIEW IS DUE IN ACCORDANCE WITH C&A

PLAN. DOCUMENTATION FOR ANNUAL REVIEW DUE IN

ACCORDANCE WITH ODAA DIRECTIVES (eMASS) AND FIVE (5) DAYS

AFTER EACH SUBSEQUENT REVIEW OR REQUIRED CHANGE.

BLK 14 - ELECTRONIC COPY SHALL IN ODAA REQUIRED COMPATIBLE

FILE FORMAT SUBMITTED PER ODAA DIRECTIVES (eMASS) AND BY

E-MAIL IN MICROSOFT OFFICE / PDF FORMAT IN ACCORDANCE WITH

CDRL DISTRIBUTION BLOCK 14.

ADDRESSEE(S) EMAIL ADDRESS: joseph.trunko@navy.mil

19 July 2017

BERGLAND.KA

RI.L.1263458067

Digitally signed by

BERGLAND.KARI.L.1263458067

Date: 2017.08.15 14:35:48 -07'00' 15 August 2017

1 1

TRUNKO.JOSEPH.M

ICHAEL.1228939990

Digitally signed by

TRUNKO.JOSEPH.MICHAEL.1228

Date: 2017.07.19 10:08:56 -07'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

MGMT

DATA MANAGEMENT SERVICES TBD

A005 CONTRACTOR'S PERSONNEL ROSTER

DI-MGMT-81834A SOW PARA 8.1, 8.2, 8.3 NSWC CORONA (AR30)

N/A C

ASGEN (See Blk 16)

N/A

20DAC (See Blk 16)

ASGEN (See Blk 16) J. Trunko (AR30) 1

0 1 0

BLK 4/5 - DI-MGMT-81834A CONTRACTOR FORMAT IS ACCEPTABLE.

SOW PARAGRAPH(S) 8.1, 8.2 AND 8.3 ARE MANDATORY TO THIS

REQUIREMENT.

BLK 9 - USE THE FOLLOWING: "DISTRIBUTION STATEMENT C.

DISTRIBUTION AUTHORIZED TO U.S. GOVERNMENT AGENCIES AND

THEIR CONTRACTORS ONLY. (REASON: ADMINISTRATIVE USE).

OTHER REQUESTS FOR THIS DOCUMENT SHALL BE REFERRED TO

NAVAL SURFACE WARFARE CENTER, CORONA DIVISION, CORONA

CA."

BLK 10, 13 - REPORTS SUBMITTED MONTHLY NO LATER THAN THE

10TH DAY OF THE MONTHLY REPORTING PERIOD. AND AS

GENERATED WHEN PERSONNEL CHANGES OCCUR, SUBMITTED NO

LATER THAN THE 10TH DAY AFTER CHANGE IN PERSONNEL HAS

OCCURRED.

BLK 12 - THE REPORTING PERIOD WILL BE FROM THE FIRST TO LAST

BUSINESS DAY OF EACH MONTH. FIRST SUBMISSION BEGINNING

WITHIN 20 BUSINESS DAYS AFTER EFFECTIVE DATE OF ORDER.

BLK 14 - ELECTRONIC COPY SHALL BE BY E-MAIL IN MICROSOFT

OFFICE / PDF FORMAT IN ACCORDANCE WITH CDRL DISTRIBUTION

BLOCK 14. ADDRESSEE(S) EMAIL ADDRESS: joseph.trunko@navy.mil

19 July 2017

BERGLAND.KA

RI.L.1263458067

Digitally signed by

BERGLAND.KARI.L.1263458067

Date: 2017.08.15 15:13:41 -07'00' 15 August 2017

1 1

TRUNKO.JOSEPH.M

ICHAEL.1228939990

Digitally signed by

TRUNKO.JOSEPH.MICHAEL.1228

Date: 2017.07.19 10:11:11 -07'00'

DATA ITEM DESCRIPTION

Title: DOD Information Assurance Certification and Accreditation Process (DIACAP) and

Risk Management Framework (RMF) Deliverable Data

Number: DI-MGMT-82000 Approval Date: 20151014

AMSC Number: 9594 Limitation:

DTIC Applicable: GIDEP Applicable:

Office of Primary Responsibility: AS Project Number: MGMT-2015-021

Applicable Forms:

Use/relationship: The DIACAP and RMF Deliverable Data will be used to satisfy the requirements of the DIACAP and/or RMF process.

This Data Item Description (DID) contains the format, content, and intended use information for the data product resulting from the work task described by the contract.

Requirements:

1. Format. The DIACAP and/or RMF artifacts shall be delivered in a format approved by the

Government’s Designated Accrediting Authority (DAA), Authorizing Official (AO), or Information

Systems Security Manager (ISSM).

2. Content. The content of the DIACAP and/or RMF artifacts shall contain the necessary artifacts required by the DAA, AO, or ISSM to successfully achieve Platform IT Risk Approval (PRA), Interim Authority to Test (IATT), Interim Authority to Operate (IATO), or Authority to Operate

(ATO).

2.1 Introduction. This section shall contain a narrative of the DIACAP/RMF package content.

2.1.1 IATT Request. The IATT Request shall use the approved DAA, AO, or ISSM format. The

IATT Request shall identify the ‘who’, ‘what’, ‘why’, ‘where’, ‘when’, and ‘how’ of the requested

Test event. IATT Request shall be delivered not less than 30 days prior to the start of the Test

Event.

2.1.2 Certification and Accreditation (C&A) or Security Plan. The C&A or Security Plan shall use the approved DAA, AO, or ISSM format. The C&A Plan shall contain at a minimum, System

Information, Mission Description, Concept of Operations (CONOPS), Environment, Operating and

Computing Environment, Physical Security Measures, Facilities Descriptions, Threat Analysis, System Architecture Description, Components, Configurations, Accreditation Boundaries, Connection Process Guide (CPG) Compliant Network Diagrams, External Interfaces and Data Flow, Internal Data Flow, Contingency Plan, Incident Response Plan, User Descriptions and Clearances, Security Roles, Hardware Lists, Software Lists, Ports, Protocols, and Services (PPS), Configuration

Management Plan, Information Assurance Vulnerability Management (IAVM) Plan, and C&A Tasks and Milestones. The C&A Plan shall be approved and signed by the ISSM, User Rep, Program

Manager (PM), and DAA or AO.

Source: https://assist.dla.mil -- Downloaded: 2016-06-17T23:06Z Check the source to verify that this is the current version before use.

DI-MGMT-82000

2.1.3 C&A Project Plan. The C&A Project Plan shall use the approved DAA, AO, or ISSM format.

The C&A Project Plan shall be approved and signed by the ISSM, Echelon II Representative, and

PM. The C&A Project Plan shall define the various C&A Tasks and Milestones needed to achieve

PRA, IATT, IATO, or ATO.

2.1.4 Collaboration Brief. The Collaboration Brief shall use the approved DAA, AO, or ISSM format. The Collaboration Brief is submitted with the DIACAP/RMF package and is used to describe the System and System Risk during the Collaboration meeting.

2.1.5 DIACAP Implementation Plan (DIP). The DIP shall use the approved DAA, AO, or ISSM format. The DIP shall be used during the DIP Concurrence meeting with the Echelon II, Navy CA, and ODAA. The DIP shall define which IA Controls (IACs) will be ‘Implemented’, ‘Inherited’, ‘Non-Compliant’, or ‘Not Applicable’. The DIP shall be approved by the DAA, AO, and ISSM prior to execution of the IA Test Plan.

2.1.6 PIT Implementation Plan (PIP). The PIP shall use the approved DAA, AO, or ISSM format.

The PIP shall be used during the PIT Concurrence meeting with the Echelon II, Navy CA, and

ODAA. The PIP shall define which IACs will be ‘Implemented’, ‘Inherited’, ‘Non-Compliant’, or

‘Not Applicable’. The PIP shall be approved by the DAA, AO, and ISSM prior to execution of the

IA Test Plan.

2.1.7 IA Test Plan. The IA Test Plan shall use the approved DAA, AO, or ISSM format. The IA

Test Plan shall define all required Vulnerability Scans, Security Technical Implementation Guides

(STIGs), Security Readiness Guides (SRGs), Secure Content Automation Protocol (SCAP) benchmarks, and IA Controls or Security Overlays to be applied to the System. The IA Test Plan shall be approved by the DAA, AO, and ISSM during the DIP or PIP Concurrence Meeting.

2.1.8 PIT Designation Request. The PIT Designation Request shall use the approved DAA, AO, or

ISSM format. The PIT Designation Request is the formal request to the DAA or AO that the System shall be designated as Platform IT (versus an Information System (IS)). The PIT Designation

Request shall be approved and a PIT Designation Letter shall be signed by the DAA or AO prior to the execution of the IA Test Plan.

2.1.9 PIT Determination Brief. The PIT Determination Brief shall use the approved DAA, AO, or

ISSM format. The PIT Determination Brief shall be used in conjunction with the PIT Designation

Request to formally request the System be designated Platform IT (versus and Information System).

2.1.10 Plan of Action and Milestones (POA&M). The POA&M shall use the approved DAA, AO, or ISSM format. The POA&M shall be considered a ‘living’ document and shall regularly be updated throughout the entire lifecycle of the System through Decommission. The POA&M shall contain all Not Applicable IA Controls, All Non-Compliant IA Controls, and all Non-Compliant

Vulnerability Findings as identified in the Vulnerability Scans, STIGs, SRGs, and SCAP

Benchmarks. At a minimum, the POA&M shall be updated monthly.

2.1.11 Privacy Impact Assessment (PIA). The PIA shall use the approved DAA, AO, or ISSM format. The PIA shall be approved and signed by the ISSM, PM, and the Command PIA Officer.

2.1.12 Vulnerability Scans. In accordance with the approved IA Test Plan, the System shall be scanned using the approved vulnerability scanning tools as identified by the DAA, AO, or ISSM.

DI-MGMT-82000

The vulnerability scanner shall be updated with the latest signatures and scanning engines prior to the execution of each vulnerability scan. At a minimum, vulnerability scans shall be conducted monthly against the System. Non-compliant findings shall be documented in the System POA&M on a minimum monthly basis. At a minimum, vulnerability scans shall be submitted electronically to the

ISSM or uploaded into the DIACAP/RMF package. Vulnerability scans shall be handled in accordance with the System’s classification level. Vulnerability reports shall be in a format approved by the DAA, AO, or ISSM.

2.1.13 STIGs, SRGs, SCAP Benchmarks. In accordance with the approved IA Test Plan, the

System shall be hardened using the required and approved STIGs, SRGs, and SCAP Benchmarks.

Non-compliant STIG, SRG, and SCAP Benchmark findings shall be documented in the System

POA&M on a minimum monthly basis. Updates to the STIGs, SRGs, and SCAP Benchmarks are released on a monthly, quarterly, and yearly basis. Updates to the STIGs, SRGs, and SCAP

Benchmarks shall be implemented into the System as they are released. Non-compliant STIG, SRG, and SCAP Benchmark findings shall be documented in the System POA&M on a minimum monthly basis. STIG, SRG, and SCAP Benchmark artifacts shall be provided in a format approved by the

DAA, AO, or ISSM. STIG, SRG, and SCAP Benchmark artifacts shall be handled in accordance with the System’s classification level. At a minimum, STIG, SRG, and SCAP Benchmarks shall be submitted electronically to the ISSM or uploaded into the DIACAP/RMF Package on a minimum monthly basis.

2.1.14 Scorecard. The Scorecard shall use the approved DAA, AO, or ISSM format. The

Scorecard shall be maintained and updated on a minimum monthly basis.

2.1.15 Contingency Plan. The Contingency Plan shall use the approved DAA, AO, or ISSM format.

The Contingency Plan shall be submitted in conjunction with the System’s C&A Plan. The

Contingency Plan shall be approved and signed by the PM, ISSM, and DAA or AO.

2.1.16 IAVM Plan. The IAVM Plan shall use the approved DAA, AO, or ISSM format. The IAVM

Plan shall be submitted in conjunction with the System’s C&A Plan. The IAVM Plan shall be approved and signed by the PM, ISSM, and DAA or AO.

2.1.17 Cyber Security Waivers. Cyber Security Waivers shall use the approved DAA, AO, or ISSM format. All Cyber Security Waivers shall be approved and signed by the ISSM, PM, and First Flag or Equivalent prior to submission to the DAA or AO.

END OF: DI-MGMT-82000

DATA ITEM DESCRIPTION

Title: CONTRACTOR'S PERSONNEL ROSTER

Number: DI-MGMT-81834A Approval Date: 20130118 AMSC Number: N9316 Limitation: N/A DTIC Applicable: No GIDEP Applicable: N/A Office of Primary Responsibility: SH/MS10 Applicable Forms: N/A

Use/relationship:

This roster shall be used to list all contractor personnel assigned to the contract.

This Data Item Description (DID) contains the content and preparation instructions for data product resulting from the work task specified in the contract.

Requirements:

1. Format. The Roster shall be in contractor’s format.

2. Content. The Roster shall contain an alphabetical listing of the names of all contractor personnel assigned to the contract.

2.1 The roster shall identify the following for each employee:

a. Change Status: Add/Change/Remove

b. Start Date

c. End Date

d. First Name

e. Middle Name

f. Last Name

g. Position Title

h. Email Address

i. Work Phone Number

j. Physical Work Location – Base Name

k. Physical Work Location - City

l. Physical Work Location - State

m. Physical Work Location – Building Number

n. Physical Work Location – Room Number

o. Contract Number

p. Contract Name

q. Contracting Supervisor

r. Government Support POC

s. Supporting Code

2.2 The roster shall identify work schedules for full time and part time employees and shall include current CAC and clearance information for each.

3. End of DI-MGMT-81834A.

File details come from the government source that posted it. Updated Nov 14, 2017.