★ America V2AuditLine ALPHA

AuditLine › DOT OIG › Office of the Secretary of Transportation

DOT OIG recommendation IT2023043-17

Direct and require confirmation of completion from FAA's cloud-based system owner for the FAA Cloud Services—Infrastructure-as-a-service and…

ClosedThe publisher's status, as reported by DOT Office of Inspector General in the file read .

The recommendation, in the publisher's words

Direct and require confirmation of completion from FAA's cloud-based system owner for the FAA Cloud Services—Infrastructure-as-a-service and Platform-as-a-Service to: a. Incorporate flaw remediation into ongoing configuration management processes. b. Develop and implement a process to regularly manage malicious code protection to detect and eradicate malicious code at the entry point for its Infrastructure-as-a-service and Platform-as-a-Service. c. Develop and implement a change control process and use baseline configuration settings and document configuration settings to establish a basis for future builds, releases, and/or changes. d. Develop and implement a process to perform an automated review of network accounts or implement an alternative method for identifying users on the network in real-time. e. Develop and implement a process to require the most current cryptographic mechanisms to protect data during network transmission to provide complete boundary protection and reduce the risk of compromise. f. Develop and implement a process to encrypt data transmitted within the Infrastructure-as-a-service environment to reduce the risk of compromise and data exposure. g. Develop and implement a process to review vulnerability scans results and remediate vulnerabilities within specified timeframes as required by FAA's security handbook.
Responsible agency
Office of the Secretary of Transportation
Issued
August 30, 2023
Report
DOT’s Cloud-Based Systems’ Security Weaknesses Hinder Its Transition to a Zero Trust Architecture (IT2023043) · find it at DOT OIG
Closed
June 6, 2025 (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

  1. Issued by DOT OIG. (publisher's date)
  2. Closed, with status “Closed”. (publisher's date)
  3. 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

20 more, of which 10 are open in the publisher's file.

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.