AuditLine › DOT OIG › Office of the Secretary of Transportation
DOT OIG recommendation FI2011022-1
Address these policy and procedural weaknesses: Develop procedural guidance for the C&A process. In addition, modify existing certification and…
The recommendation, in the publisher's words
Address these policy and procedural weaknesses: Develop procedural guidance for the C&A process. In addition, modify existing certification and accreditation policy and procedures to address inheritance of common information security controls, and to provide procedural guidance to modes. Correct POA&M policy to prioritize weaknesses in a way that ensures that high priority weaknesses are resolved before medium priorities, and medium ones before low ones. In addition, develop procedural guidance to ensure consistency of the POA&M process and to facilitate CIO's oversight and management of weaknesses. In conjunction with the modes, develop procedural guidance for tracking and training personnel with significant security responsibilities. This guidance should address maintaining complete inventories of such personnel, and the training needed and provided.Enhance high-level policy with procedural guidance to ensure consistency of the network accounts and identity management. In conjunction with the Assistant Secretary for Administration, complete Department-wide PIV operating procedures, including procedures to terminate PIV cards.Review and revise all configuration management policy and develop specific details for activities that are common across the department. As part of this effort, develop procedural guidance that would define requirements for OAs to use when developing configuration management procedures specific to their operation.Develop procedural guidance that would define requirements for OAs to use when developing incident handling procedures specific to their operation.Enhance policy and procedural guidance to incorporate detailed guidance for managing, monitoring and reporting FDCC compliance, including the use of SCAP tools to ensure FDCC compliance.Once policy adequately addresses contractor oversight per Recommendation 4 of last year's report, develop relevant procedural guidance. This policy should establish the criteria and guidelines for DOT's identification and reporting of contractor systems consistent with OMB requirements. Enhance high-level policy with procedural guidance to ensure remote access and wireless networking is authorized, managed and monitored in compliance with OMB, NIST and DOT policies.
- Responsible agency
- Office of the Secretary of Transportation
- Issued
- November 15, 2010
- Report
- Timely Actions Needed to Improve DOT's Cybersecurity (FI2011022) · find it at DOT OIG
- Closed
- August 1, 2011 (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
26 more, of which 0 are open in the publisher's file.
- Implement a practice to review OA specific incident handling procedures to ensure that they adhere to the departmental policy.DOT OIG FI2011022-10 · issued Nov 15, 2010 · closed Oct 2, 2012Closed
- Implement a process to review reported incidents to ensure timely reporting to US-CERT. In addition, provide monitoring of incidents reported to ensure all required data in the tracking…DOT OIG FI2011022-11 · issued Nov 15, 2010 · closed Oct 19, 2011Closed
- Review FHWA, FMCSA, FRA, FTA and RITA automated scans confirming timely resolution of vulnerabilities. If deficiency is found require OA to provide corrective action and to update plan of…DOT OIG FI2011022-12 · issued Nov 15, 2010 · closed Sep 4, 2013Closed
- Require OAs to reconcile their contractor records with DOT security department and update their records accordingly. Monitor and report to the Deputy Secretary, Operating Administrations…DOT OIG FI2011022-13 · issued Nov 15, 2010 · closed Oct 2, 2012Closed
- Identify and implement automated tools to better track contractors and training requirements.DOT OIG FI2011022-14 · issued Nov 15, 2010 · closed Dec 3, 2021Closed
- In conjunction with the MARAD, create a POAM for each system that is missing a certification and accreditation. This POAM should be properly prioritized to ensure this critical matter is…DOT OIG FI2011022-15 · issued Nov 15, 2010 · closed Mar 25, 2011Closed
- In conjunction with MARAD, promptly update Cyber Security Assessment and Management (CSAM) system to reflect its current system inventory and related information (including status of…DOT OIG FI2011022-16 · issued Nov 15, 2010 · closed Apr 26, 2011Closed
- Work with MARAD to finalize agreements with C&A service providers to certify MARAD systems.DOT OIG FI2011022-17 · issued Nov 15, 2010 · closed Feb 24, 2011Closed
- Review the results of OA assessments to determine an accurate inventory of contractor systems.DOT OIG FI2011022-18 · issued Nov 15, 2010 · closed Feb 11, 2016Closed
- Work with the Department's acquisition personnel to develop common contract language that requires IT contractors to enforce applicable FISMA and OMB requirements. Once this language is…DOT OIG FI2011022-19 · issued Nov 15, 2010 · closed Jul 18, 2012Closed
- To the extent the OAs require their own guidance, review guidance to verify compliance with department policies and procedures.DOT OIG FI2011022-2 · issued Nov 15, 2010 · closed Oct 2, 2012Closed
- Research and standardize automated tools that will proactively monitor remote devices connecting to DOT networks.DOT OIG FI2011022-20 · issued Nov 15, 2010 · closed Jun 4, 2013Closed
- Conduct tests of remote access solutions to ensure they comply with Federal requirements and DOT guidance.DOT OIG FI2011022-21 · issued Nov 15, 2010 · closed Aug 5, 2013Closed
- In conjunction with the Assistant Secretary for Administration, develop a Department-wide implementation plan that specifies resources needed, responsible parties, strategies for risk…DOT OIG FI2011022-22 · issued Nov 15, 2010 · closed Aug 1, 2011Closed
- Implement the use of PIV cards as the primary authentication mechanism to support multi-factor authentication at the system and application level for all DOT's employees and contractors.DOT OIG FI2011022-23 · issued Nov 15, 2010 · closed Sep 4, 2015Closed
- Perform periodic reviews of active user accounts and network devices to identify accounts that need to be disabledDOT OIG FI2011022-24 · issued Nov 15, 2010 · closed Jul 18, 2012Closed
- Work with OAs to identify and logically segregate user accounts and service (role) accounts.DOT OIG FI2011022-25 · issued Nov 15, 2010 · closed Oct 2, 2012Closed
- Work with OAs to implement automated mechanisms to disable inactive accounts, as specified by DOT policies, and to audit account creation, modification, disabling, and termination actions.DOT OIG FI2011022-26 · issued Nov 15, 2010 · closed Oct 2, 2012Closed
- Educate and assist OAs in implementing dual accounts for administrators. Subsequently, conduct reviews to determine that all DOT GSSs use these accounts.DOT OIG FI2011022-27 · issued Nov 15, 2010 · closed Jul 15, 2014Closed
- Implement a quality assurance process to review OA specific configuration management procedures to ensure that they adhere to the departmental policy and Federal requirements.DOT OIG FI2011022-3 · issued Nov 15, 2010 · closed Oct 2, 2012Closed
- Implement a process to review OAs security configuration management practices and software scanning capabilities. Provide monitoring of OAs practices to ensure they are adhering to the…DOT OIG FI2011022-4 · issued Nov 15, 2010 · closed Jun 4, 2013Closed
- Require OST to implement required system patches on their Delphi system.DOT OIG FI2011022-5 · issued Nov 15, 2010 · closed Aug 1, 2011Closed
- Conduct scanning of all DOT networks to ensure compliance with FDCC requirements. In addition, review results of modal SCAP compliance scans to identify and resolve incorrect FDCC settings.DOT OIG FI2011022-6 · issued Nov 15, 2010 · closed Jun 4, 2013Closed
- Require and approve deviation requests for those non-conforming settings that are truly needed and for which risks have been mitigated and accepted.DOT OIG FI2011022-7 · issued Nov 15, 2010 · closed Oct 2, 2012Closed
- Conduct periodic tests to assess FDCC compliance and deployment of patches, including service packs.DOT OIG FI2011022-8 · issued Nov 15, 2010 · closed Jun 4, 2013Closed
- Analyze the incorrect FDCC configuration settings identified in our testing, and for those that do not have approved deviations, require OAs to create POA&Ms to correct the settings.DOT OIG FI2011022-9 · issued Nov 15, 2010 · closed Jun 4, 2013Closed
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.