Back to Network
6
Shared Docs
6
Same-Page
6 / 6
Mentions
Document Mentions (6 shared documents)
2 mentions1 same-page
Page ?Same page
aining baseline configurations and inventories of Covered Information Systems, including hardware, software, firmware, and documentation, throughout the Information System Development Lifecycle, and establishing and enforcing security configuration settings for IT products employed in Information Systems; 7. Ensuring appropriate contingen
vide written updates to the DOJ CO regarding the status of the Security Incident at least every three (3) calendar days until in- formed otherwise by the DOJ CO. E. All determinations regarding whether and when to notify individuals and/or federal agencies potentially affected by a Secur- ity Incident will b
2 mentions1 same-page
Page ?Same page
aining baseline configurations and inventories of Covered Information Systems, including hardware, software, firmware, and documentation, throughout the Information System Development Lifecycle, and establishing and enforcing security configuration settings for IT products employed in Information Systems; 7. Ensuring appropriate contingen
vide written updates to the DOJ CO regarding the status of the Security Incident at least every three (3) calendar days until in- formed otherwise by the DOJ CO. E. All determinations regarding whether and when to notify individuals and/or federal agencies potentially affected by a Secur- ity Incident will b
2 mentions1 same-page
Page ?Same page
aining baseline configurations and inventories of Covered Information Systems, including hardware, software, firmware, and documentation, throughout the Information System Development Lifecycle, and establishing and enforcing security configuration settings for IT products employed in Information Systems; 7. Ensuring appropriate contingen
vide written updates to the DOJ CO regarding the status of the Security Incident at least every three (3) calendar days until in- formed otherwise by the DOJ CO. E. All determinations regarding whether and when to notify individuals and/or federal agencies potentially affected by a Secur- ity Incident will b
Sponsored
2 mentions1 same-page
Page ?Same page
aining baseline configurations and inventories of Covered Information Systems, including hardware, software, firmware, and documentation, throughout the Information System Development Lifecycle, and establishing and enforcing security configuration settings for IT products employed in Information Systems; 7. Ensuring appropriate contingen
vide written updates to the DOJ CO regarding the status of the Security Incident at least every three (3) calendar days until in- formed otherwise by the DOJ CO. E. All determinations regarding whether and when to notify individuals and/or federal agencies potentially affected by a Secur- ity Incident will b
2 mentions1 same-page
Page ?Same page
aining baseline configurations and inventories of Covered Information Systems, including hardware, software, firmware, and documentation, throughout the Information System Development Lifecycle, and establishing and enforcing security configuration settings for IT products employed in Information Systems; 7. Ensuring appropriate contingen
vide written updates to the DOJ CO regarding the status of the Security Incident at least every three (3) calendar days until in- formed otherwise by the DOJ CO. E. All determinations regarding whether and when to notify individuals and/or federal agencies potentially affected by a Secur- ity Incident will b
2 mentions1 same-page
Page ?Same page
aining baseline configurations and inventories of Covered Information Systems, including hardware, software, firmware, and documentation, throughout the Information System Development Lifecycle, and establishing and enforcing security configuration settings for IT products employed in Information Systems; 7. Ensuring appropriate contingen
vide written updates to the DOJ CO regarding the status of the Security Incident at least every three (3) calendar days until in- formed otherwise by the DOJ CO. E. All determinations regarding whether and when to notify individuals and/or federal agencies potentially affected by a Secur- ity Incident will b
Sponsored
Mutual Connections (79)
Entities connected to both the Information System Development Lifecycle and the DOJ CO.
the Potential Breach
ORGANIZATION9 w/ the·6 w/ the
Potential Security Breach
ORGANIZATION9 w/ the·6 w/ the
Potential Covered Information System Security Breach
ORGANIZATION9 w/ the·6 w/ the
Breach
ORGANIZATION9 w/ the·6 w/ the
the Confirmed Breach
ORGANIZATION9 w/ the·6 w/ the
the Contacting Officer's Representative
ORGANIZATION9 w/ the·6 w/ the
the United States Government
ORGANIZATION9 w/ the·6 w/ the
Homeland Security
ORGANIZATION9 w/ the·6 w/ the
NG
Notification Guidelines
PERSON9 w/ the·6 w/ the
the Office of Inspector General
ORGANIZATION9 w/ the·6 w/ the
FE
FedRAMP
PERSON9 w/ the·6 w/ the
the Scope of Work
ORGANIZATION9 w/ the·6 w/ the
the Department of Defense
ORGANIZATION9 w/ the·6 w/ the
Liability - Award
ORGANIZATION9 w/ the·6 w/ the
the Contracting Staff/Focal Point
ORGANIZATION9 w/ the·6 w/ the
Samantha Power
PERSON9 w/ the·6 w/ the
Commodity or Services
ORGANIZATION9 w/ the·6 w/ the
the Presence of Hazardous Material
ORGANIZATION9 w/ the·6 w/ the
Unpaid Delinquent Tax Liability - Award
ORGANIZATION9 w/ the·6 w/ the
SGT-AMS
ORGANIZATION9 w/ the·6 w/ the