AuditLine › DOT OIG › Office of the Secretary of Transportation
DOT OIG recommendation FI2015009-3
Establish an enterprise-wide strategy that DOT components must adhere to implement and monitor Information Security Continuous Monitoring for…
The recommendation, in the publisher's words
Establish an enterprise-wide strategy that DOT components must adhere to implement and monitor Information Security Continuous Monitoring for Continuous Diagnostics and Mitigation requirements as outlined in OMB policy and NIST guidance.
- Responsible agency
- Office of the Secretary of Transportation
- Issued
- November 14, 2014
- Report
- DOT Has Made Progress but Significant Weaknesses in Its Information Security Remain (FI2015009) · find it at DOT OIG
- Closed
- February 11, 2016 (publisher's date)
“Open” and “closed” are the publisher's words. AuditLine repeats them with the date it read them. It does not check whether a recommendation was carried out, and a closed recommendation is not proof that a problem was fixed.
Dated history
- Issued by DOT OIG. (publisher's date)
- Closed, with status “Closed”. (publisher's date)
- First recorded by AuditLine. (start of AuditLine's own history for this record)
Dates marked "publisher's date" come from the publisher's file. AuditLine's own observations begin November 10, 2026 and are added each time the publisher's file changes.
Other recommendations from this report
15 more, of which 0 are open in the publisher's file.
- Revise the Department's AECM policy to develop procedural requirements that document activities components must complete to report and mitigate deficiencies identified through continuous…DOT OIG FI2015009-1 · issued Nov 14, 2014 · closed Feb 11, 2016Closed
- Work with the CSMC and individual components (including COE) to develop service level agreements needed to define responsibilities between CSMC and the components. These agreements should…DOT OIG FI2015009-10 · issued Nov 14, 2014 · closed Sep 28, 2018Closed
- Revise DOT policy to provide specific guidance for what data, format of data, and how often components should report system security status to the Authorizing Official throughout the…DOT OIG FI2015009-11 · issued Nov 14, 2014 · closed Feb 11, 2016Closed
- Work with FAA to revise their plan to effectively transition the remaining 32,266 users to require unprivileged PIV login. Create a POA&M with a planned completion date to monitor and…DOT OIG FI2015009-12 · issued Nov 14, 2014 · closed Feb 11, 2016Closed
- Develop a plan to periodically review waived accounts to determine if they should be transitioned to PIV required status. Create a POA&M with a planned completion date to monitor and track…DOT OIG FI2015009-13 · issued Nov 14, 2014 · closed Oct 6, 2015Closed
- Work with components to revise their plans to effectively transition the remaining users to require privileged PIV login. Create a POA&M with a planned completion date to monitor and track…DOT OIG FI2015009-14 · issued Nov 14, 2014 · closed Oct 6, 2015Closed
- Work with components to develop or revise their plans to effectively transition the remaining information systems to required PIV login. Create a POA&M with planned completion dates to…DOT OIG FI2015009-15 · issued Nov 14, 2014 · closed Aug 10, 2022Closed
- Work with the Director of DOT Security to develop or revise their plan to effectively transition the remaining facilities to required PIV cards.DOT OIG FI2015009-16 · issued Nov 14, 2014 · closed Aug 5, 2020Closed
- Implement the revised AECM policy and procedural guidance and provide and work with components to establish planned action dates to mitigate deficiencies in their ISCM reporting and…DOT OIG FI2015009-2 · issued Nov 14, 2014 · closed Feb 11, 2016Closed
- Revise the Department's policy to address the mandatory use of a toolset and requisite processes to perform the Information Security Continuous Monitoring tasks outlined by OMB.DOT OIG FI2015009-4 · issued Nov 14, 2014 · closed Feb 11, 2016Closed
- Start planning and assessing impact of the security requirements that will be affected by NIST SP 800-53 revision 4 and NIST SP 800-53A revision 4.DOT OIG FI2015009-5 · issued Nov 14, 2014 · closed Aug 17, 2018Closed
- Revise DOT Cybersecurity policy and guidance to incorporate new or updated security requirements defined by NIST SP 800-53 revision 4 and NIST SP 800-53A revision 4.DOT OIG FI2015009-6 · issued Nov 14, 2014 · closed Feb 11, 2016Closed
- Work with components to develop a plan to address NIST 800-53 revision 4 requirements for their systems. Create a POA&M with planned completion date to monitor and track progress.DOT OIG FI2015009-7 · issued Nov 14, 2014 · closed Feb 11, 2016Closed
- Work with the components to develop a plan to complete annual SAT training within plan milestones and improve tracking. Assess training periodically to determine if the component will meet…DOT OIG FI2015009-8 · issued Nov 14, 2014 · closed Mar 1, 2023Closed
- Work with FAA to ensure automated scripts are properly configured to disable inactive user accounts in a timely manner. Create a POA&M with a planned completion date to monitor and track…DOT OIG FI2015009-9 · issued Nov 14, 2014 · closed Oct 6, 2015Closed
Source
Open this report in DOT OIG's tracker This publisher's records (CSV)
Official export: https://www.oig.dot.gov/recommendation-dashboard/export?page&_format=csv. File read , 3,436 rows,
SHA-256 6406a142cdf501ec…. DOT OIG's status and dollar figures are the publisher's own claims. Recommendations it marks sensitive are listed without their text.