Breadcrumb

VA Applications Lacked Federal Authorizations, and Interfaces Did Not Meet Security Requirements

Report Information

Issue Date
Report Number
20-00426-02
VISN
State
District
VA Office
Information and Technology (OIT)
Report Author
Office of Audits and Evaluations
Report Type
Review
Report Topic
Information Technology and Security
Major Management Challenges
Leadership and Governance
Recommendations
4
Questioned Costs
$0
Better Use of Funds
$0
Congressionally Mandated
No

Summary

Summary
The Federal Risk and Authorization Management Program (FedRAMP) standardizes security and risk assessments for cloud technologies for federal agencies, including VA. In April 2019, the VA Office of Inspector General (OIG) received allegations that VA’s Office of Information and Technology’s (OIT’s) Project Special Forces (PSF) was not following FedRAMP policies or VA policy for deploying software-as-a-service (SaaS) applications. The OIG found that OIT granted security authorizations for applications that were not authorized by FedRAMP. Eight of the nine applications cited by the complainant were in use on the VA network—some without FedRAMP or VA authorization. Another three applications were approved to operate on VA’s network without FedRAMP authorization. The OIG did not substantiate that PSF-developed applications were improperly managed outside the VA Enterprise Cloud group. However, PSF did not follow VA security requirements in developing interfaces that allow third parties to “plug into” the VA to send and retrieve data. OIT personnel stated that there was no formal OIT authorization process until April 2019. After that date, the review team did not find instances of VA-authorized applications without FedRAMP authorization. OIT staff also misunderstood the FedRAMP authorization requirements for SaaS applications containing data classified as less sensitive. Failure to comply with FedRAMP standards increases the risk that VA and veterans’ data could be compromised. The OIG made four recommendations to the acting chief information officer (1) to determine whether to prevent use of the unauthorized SaaS applications and (2) whether the reviewed applications should be authorized or reported to the Federal Chief Information Officer. The remaining recommendations were (3) to implement alerts for interface-related abuse and (4) to either use application programming interfaces that transmit sensitive information and requirements for cross-origin resource sharing or seek exceptions to the standards. VA concurred with all recommendations.

Open Recommendation Image, SquareOpenClosed and Implemented Recommendation Image, CheckmarkClosed-ImplementedNot Implemented Recommendation Image, X character'Closed-Not Implemented
No. 1
Open Recommendation Image, Square
to Information and Technology (OIT)
Review the SaaS applications named in the allegation to determine whether VA staff are still using them and whether such use is consistent with VA policy. If use is authorized, implement controls to ensure the applications go through the Federal Risk and Authorization Management Program authorization process and the VA SaaS application approval process. If use is not authorized, implement controls to prevent employees from using the SaaS applications without authority to operate.
No. 2
Closed and Implemented Recommendation Image, Checkmark
to Information and Technology (OIT)
Determine whether Federal Risk and Authorization Management Program authorization will be pursued for the IRBManager application. If the required federal authorization is not pursued, include this application in the annual certification letter to the Federal Chief Information Officer along with the appropriate rationale and proposed mitigation plan.
No. 3
Closed and Implemented Recommendation Image, Checkmark
to Information and Technology (OIT)
Implement JavaScript Object Notation Web Encryption for Lighthouse application programming interfaces that transmit sensitive information and resource-sharing requirements for cross-origin resource sharing to meet the requirements of VA Office of Information Security’s Application Programming Interface Security Pattern. Alternatively, coordinate with the Office of Information Security to determine if modifications or exceptions to security standards are warranted.
No. 4
Closed and Implemented Recommendation Image, Checkmark
to Information and Technology (OIT)
Implement alerts for application programming interface-related abuse to meet the requirements of the VA Office of Information Security’s Application Programming Interface Security Pattern.