1 . Executive Summary

The Department of Veterans Affairs (VA) mission is to serve America’s Veterans and their families with dignity and compassion, to be their principal advocate, and to ensure that they receive the medical care, benefits, social support, and lasting memorials for which they are eligible because of their service to our Nation. As part of its mission, VA shares a vast amount of Veteran and VA mission-critical privacy information. This includes sensitive personal information (SPI), such as personally identifiable information (PII) and protected health information (PHI), across the organization and with VA partners. Protecting this data, complying with applicable privacy laws, and managing privacy risks is extremely important to maintain VA’s standing as a trusted organization.

This Privacy Program Plan (PPP) supplements VA Directive 6502, VA Enterprise Privacy Program, to formally document the VA Privacy Program. It describes how VA implements Office of Management and Budget (OMB) Circular A-130, Managing Information as a Strategic Resource.

The purpose of the PPP is to provide an overview of the VA Privacy Program. This plan highlights:

  • The structure and mission of the VA Privacy Program.
  • Resources dedicated to the VA Privacy Program.
  • Role of the Senior Agency Official for Privacy (SAOP).
  • Strategic goals and objectives of the Privacy Program.
  • Program Management controls in place to meet applicable Federal privacy requirements and manage privacy risks.
  • An overview of the VA Privacy Program requirements.

This Plan serves as a high-level summary of the VA Privacy Program. The PPP is a living management document designed to accommodate changes in privacy laws, technology, requirements, and standards. VA Administrations – Veterans Health Administration (VHA), Veterans Benefits Administration (VBA) and National Cemetery Administration (NCA) – are encouraged to use it as the foundation for their own PPP when addressing Administration-specific privacy matters.

2. VA Privacy Program Strategic Goals and Objectives

Protecting privacy is fundamental to the successful accomplishment of the VA mission and to maintain the trust Veterans have in VA. The VA Privacy Program has a vision to serve as a model for privacy excellence across the federal government, providing a trusted environment that protects the privacy of Veterans, their beneficiaries and VA employees.

The VA Privacy Program strives to build and strengthen Veterans’ trust in VA by preserving privacy, oversight, and transparency in the execution of all VA activities.

To accomplish this, VA has developed four VA Privacy Program goals, each supported by specific and measurable objectives:

Goal 1: Ensure VA Maintains Compliance with Federal Privacy Laws, Regulations and Policy

VA commits to achieve excellence in privacy compliance while reducing privacy risks to Veterans, their families, and caregivers. VA develops and implements policies, procedures, and controls to comply with federal privacy laws and regulations. VA regularly reviews and updates its practices to align with evolving federal and VA guidelines, fostering a culture of accountability and integrity in handling PII.

Objective 1.1 – Increase accountability and transparency by enhancing and automating VA’s privacy compliance processes in adherence to the Privacy Act of 1974, OMB requirements, E-Government Act of 2002, and best practices. The privacy compliance process includes the Privacy Threshold Analysis (PTA), Privacy Impact Assessment (PIA), and System of Records Notices (SORNs).

Objective 1.2 – Partner with and provide sound and consistent guidance to VA Administrations and Staff Offices concerning the implementation of Federal privacy laws, regulations, and other best practices, supported by legal advice from the Office of General Counsel (OGC).

Objective 1.3 – Report privacy-related complaints and incidents systematically, process efficiently, and mitigate appropriately, according to legal requirements and VA policies and procedures.

Objective 1.4 – Implement a cycle of continuous assessment and improvement to embed and enforce privacy protections. Adhere to privacy requirements and transparency in all VA activities that have a privacy impact.

Goal 2: Manage Enterprise-wide Privacy Risk

VA is dedicated to managing privacy risks to effectively protect PII and help achieve VA’s mission. VA establishes and uses a multi-level risk management approach that addresses security and privacy risk at the organization, mission, business process, and information system levels. VA executes the Risk Management Framework (RMF) to manage privacy risks that may result from unauthorized access or disclosure of PII; the processing of PII; inadequate quality or integrity of PII; and the lack of appropriate notice, transparency, or participation. VA considers privacy as a part of the ongoing Assessment and Authorization (A&A) of information systems and that privacy risks are at an acceptable level prior to granting an Authorization to Operate (ATO) decision.

Objective 2.1 – Integrate privacy requirements and controls into the enterprise architecture, system development lifecycle, acquisition processes and system engineering processes.

Objective 2.2 – Mature privacy continuous monitoring capabilities to ensure the effective implementation and monitoring of controls to maintain situational awareness of VA’s privacy posture.

Objective 2.3 – Integrate privacy into all governance. Consider privacy as a part of the upfront assessments of Enterprise-wide policy, budget, and programmatic decision making as well as business operations, system development, and related activities.

Objective 2.4 – Establish a systematic, risk-driven process that operationalizes the “Privacy by Design” framework within VA information system development and engineering approaches.

Goal 3: Cultivate a Privacy Risk-Aware Culture

VA ensures that all personnel have a baseline understanding of federal privacy requirements by providing training for new employees and contractors and annually thereafter. These programs reinforce the privacy policy implementation and reduce the risk of privacy incidents to our Veterans, their beneficiaries, and VA employees. VA also develops and provides targeted, role-based, specialized training to employees.

Objective 3.1 – Consistently apply privacy requirements across VA workforce to ensure the protection of Veterans, their beneficiaries, and VA employee’s PII.

Objective 3.2 – Develop and deliver advanced and targeted role-based privacy training to employees, including managers, senior executives, and contractors, with assigned privacy roles and responsibilities.

Objective 3.3 – Educate the VA workforce about privacy laws, regulations, and VA policies, fostering a culture of privacy awareness within all activities.

Goal 4: Become the Best Privacy Workforce in Government

VA develops and sustains a highly skilled, diverse, and engaged privacy workforce to accomplish the privacy mission. VA ensures supervisors understand the key role they play in the recruitment, hiring, and retention efforts for privacy positions. VA leverages training and professional development opportunities to develop and manage a high-performing privacy workforce. VA provides privacy leaders and managers with insight and tools to effectively carry out performance management, organizational learning, and succession planning.

Objective 4.1 – Enhance privacy skillsets to enable a workforce capable of managing privacy risks.

Objective 4.2 – Develop workforce planning and succession strategies to ensure continuity of operations. Position the VA Privacy Program to effectively address the evolving challenges within the federal privacy landscape.

Objective 4.3 – Ensure hiring managers take advantage of flexible hiring authorities for privacy positions.

Objective 4.4 – Promote a culture of continuous learning and professional development in support of the privacy mission. Support a comprehensive Privacy Officer training approach that accelerates development and helps Privacy Officers perform better in their jobs.

3. Structure of the VA Privacy Program

The VA Office of Information and Technology (OIT) manages VA’s Privacy Program centrally. This means OIT oversees the overall direction and policies related to privacy across VA. However, the roles and responsibilities of the VA Privacy Program are distributed amongst VHA, VBA, NCA, and VA Staff Offices. Each of these administrations and offices play a part in ensuring that privacy policies and standards are upheld within their respective domains, contributing to the broader goals of the VA Privacy Program.

The VA Privacy Program has dedicated personnel resources, including VA Senior Agency Official for Privacy (SAOP), VA Chief Privacy Officer (CPO), VA Privacy Service Director, Administration Privacy Officers (PO), and VA Staff Office POs.

VA Privacy Program Organizational Chart
Figure 1:

VA Privacy Program Organizational Chart

3.1 Senior Agency Official for Privacy

According to Executive Order 13719, Establishment of the Federal Privacy Council, and the OMB Memorandum M-16-24, Role and Designations of Senior Agency Officials for Privacy, the VA Secretary designated the Assistant Secretary for Information and Technology (ASIT) and Chief Information Officer (CIO) as the VA SAOP on April 16, 2026. The SAOP is responsible for protecting privacy interests and ensuring the responsible management of PII across the agency. The SAOP is responsible for overseeing, coordinating, and facilitating VA’s compliance with privacy policies, as mandated by Federal legislation, the OMB, and as described in VA Directive 6502, Enterprise Privacy Program. The SAOP has overall responsibility and accountability to integrate privacy protections into all VA programs, technologies, policies, and procedures.

The responsibilities of the SAOP include:

  • Establishing the VA Privacy Program and providing oversight for the protection of PII.
  • Designating a senior executive as VA CPO.
  • Serving as the “Agency Steward” for the VA Privacy Program, embodying responsibility for the compliance, enforcement, accountability, and managing the protection of PII.
  • Providing guidance and oversight of the VA Privacy Program budget and advocating for privacy solutions throughout the planning, programming, budget, and execution process.
  • Ensuring adherence to the Privacy Act and Title 38 United States Code confidentiality statutes in all operations and policies of the VA Privacy Program.
  • Serving as the VA member of the Federal Privacy Council as listed in Executive Order 13719, Establishment of the Federal Privacy Council.

3.2 VA Chief Privacy Officer

According to 42 U.S.C. § 2000ee-2(a), each agency must have a CPO who assumes primary responsibility for privacy and data protection policy. On January 6, 2025, the SAOP designated the Deputy Chief Information Officer for Compliance, Risk, and Remediation as the VA CPO. The CPO has primary responsibility for implementation and sustainment of VA’s privacy program and related functions delegated by the SAOP.

The responsibilities of the CPO include:

  • Administering the VA Privacy Program on behalf of the VA SAOP.
  • Ensuring Under Secretaries, Assistant Secretaries and Other Key Officials comply with privacy laws and requirements and manage privacy risks within their realm of responsibility.
  • Implementing privacy protections commensurate with the risk and magnitude of the potential harm to individuals in all VA operations.
  • Integrating privacy and information management processes within Enterprise-level strategic and operational planning and daily business processes.
  • Ensuring compliance with information system policies and procedures outlined in VA Handbook 6500, Risk Management Framework for VA Information Systems VA Information Security Program.
  • Developing and maintaining mandatory agency-wide privacy awareness and training programs according to applicable privacy laws and policies.
  • Maintaining a central policy making role in developing and evaluating VA legislative, regulatory, and other policy proposals involving privacy issues.
  • Advising on the process for receiving, documenting, tracking, and investigating privacy complaints, incidents, and data breaches.
  • Implementing the VA privacy continuous monitoring strategy to maintain ongoing awareness of threats and vulnerabilities that may pose privacy risks. Monitor changes to information systems that create, collect, use, process, store, maintain, disseminate, disclose, or dispose of PII. Conduct privacy control assessments to verify the continued effectiveness of all privacy controls selected and implemented to comply with applicable privacy requirements and manage privacy risks.

3.3 VA Privacy Service Director

The VA Privacy Service Director reports directly to the VA Chief Privacy Officer. The VA Privacy Service Director performs the day-to-day oversight and management of the VA Privacy Program under the supervision of the SAOP and CPO.

The responsibilities of the VA Privacy Service Director include:

  • Serving as the key policy advisor on implementing federal privacy requirements to include the Privacy Act of 1974, privacy provisions of the E-Government Act of 2002, OMB Circular A-130, OMB Circular A-108, and other laws, regulations, and policies.
  • Overseeing, directing, and establishing the VA Privacy Program’s long-term goals.
  • Advising and recommending the privacy implications of VA’s planning, programming, and budgeting processes to senior officials.
  • Developing policies, procedures, programs, and materials at an Enterprise-wide level.
  • Managing VA compliance and risk management programs to include PIAs, SORNs, and computer matching agreements (CMAs).

3.4 Administration Privacy Officers

VHA, VBA, and NCA implement and manage the VA Privacy Program through the Administration-level POs designated by the Undersecretaries of Health, Benefits and Memorial Affairs, respectively. These POs develop Administration policy and implementation guidance that assigns responsibilities and duties to all Privacy Officers within their respective areas.

Administration PO responsibilities include:

  • Developing and implementing Administration-wide privacy policies and procedures.
  • Providing input to the VA Privacy Service Director to develop privacy policies and initiatives. After implementing these policies, providing feedback on their effectiveness.
  • Implementing the VA Privacy Program within their respective areas.
  • Understanding and applying Federal law, regulations, and VA Directives related to privacy.
  • Serving as advisors on all aspects of privacy in their Administration.
  • Creating and promoting a proactive privacy environment within their Administration.
  • Determining the need for field-based POs within their Administrations.

Providing instruction regarding responsibilities and requirements to implement the VA Privacy program within field-based facilities.

3.5 VA Privacy Officers

VA requires the head of every VA Staff Office and local level Administration (VHA, VBA and NCA) Office to designate a PO. The PO is responsible for establishing and maintaining a sustainable local Privacy Program that complies with VA and Administration-level privacy policies and procedures. The PO effectively manages privacy risks in the information systems and operations within their realm of responsibilities.

VA PO responsibilities are:

  • Establishing and implementing privacy policies.
  • Carrying out their duties in accordance with VA Directive 6509, Duties of Privacy Officers.
  • Understanding and applying federal law, regulations, guidance, and VA policy related to privacy.
  • Serving as advisor and primary contact for privacy.
  • Administering privacy training and awareness programs within their realm of responsibility.
  • Working with the appropriate parties to identify, publish, and update SORNS in accordance with VA Handbook 6300.5, Procedures for Establishing and Maintaining Privacy Act Systems of Records.
  • Collaborating with local Record Officers or Records Liaison Officers to implement processes for proper retention and disposal of records that contain PII.
  • Providing notice through Privacy Act statements when the VA collects information from members of the public.
  • Creating and promoting a proactive privacy environment within their organizations.
  • Responding appropriately to all privacy complaints under their purview of responsibility.
  • Reporting all actual or suspected privacy incidents into the designated data breach reporting system within one hour of discovery or notification.
  • Completing all assigned PTAs and PIAs in accordance with VA Directive 6508, Implementation of Privacy Threshold Analysis and Privacy Impact Assessment.
  • Including privacy language in contracts to properly safeguard PII in accordance with VA 6500.6, Contract Security.
  • Providing support to Information System Owners (ISO), Information System Security Officer (ISSO) and VA Privacy Service to address privacy-related controls in accordance with VA Handbook 6500, Risk Management Framework for VA Information Systems VA Information Security Program and other VA-issued control guidance and policies.

4. Privacy Principles and Policy Framework

The VA Privacy Program is guided by established privacy principles, federal laws, regulations, government-wide requirements, and VA policies that provide the foundation for how we protect and manage PII.

Together, these principles and requirements help ensure privacy is considered throughout the information lifecycle and incorporated into VA programs, systems, business processes, and operations. They provide a consistent framework for protecting personal information, managing privacy risks, promoting transparency and accountability, and meeting VA’s privacy responsibilities.

4.1 Fair Information Practice Principles (FIPPs)

VA uses the FIPPs when evaluating information systems, processes, programs, and activities that affect individual privacy. The FIPPs include:

Openness. When VA collects personal data from an individual, VA will inform him or her of the intended uses of the data, the disclosures that will be made, the authorities for the data collection, and whether the collection is mandatory or voluntary. No VA office will collect data subject to the Privacy Act unless a Privacy Act system notice has been published in the Federal Register and posted on the VA SORNs Website, available at: Privacy Act System of Records Notices.

Individual Participation. Unless VA has claimed an exemption from the Privacy Act, everyone will be granted access to his or her records, upon request; to the extent permitted by law and provided with a list of disclosures made outside VA; and provided the opportunity to make corrections to his or her file if it is shown to be in error.

Limited Collection. VA will collect only those personal data elements required to fulfill an official function or mission grounded in law. Those collections will be conducted by lawful and fair means.

Limited Retention. VA will retain personal information only for as long as necessary to fulfill the purposes for which it is collected. Records will be destroyed in accordance with established National Archives and Records Administration (NARA) and VA records management principles.

Data Quality. VA will make every effort to maintain only accurate, relevant, timely and complete data about individuals.

Limited Internal Use. VA will use personal data for lawful purposes only. Access to any personal data will be limited to those individuals within VA with an official need for the data.

Disclosure. VA personnel will zealously guard all personal data to ensure that all disclosures are made with written permission or in strict accordance with privacy statutes.

Security. All personal data will be protected by safeguards appropriate to ensure security and confidentiality. Electronic systems will be periodically reviewed for compliance with the security principles of the Privacy Act, the Computer Security Act, Health Insurance Portability and Accountability Act (HIPAA), and related statutes. Electronic collection of information will only be conducted in a safe and secure manner.

Accountability. VA, its employees, and contractors are subject to civil and criminal penalties for certain breaches of privacy. VA officials will be diligent in sanctioning individuals who violate privacy rules.

Challenging Compliance. An individual may challenge VA if he or she believes that VA has failed to comply with these principles, privacy statutes, or the rules in SORN.

4.2. VA Privacy Policies

VA issues policy documents (referred to as Directives, Handbooks and Notices) to establish the principles, requirements, and responsibilities for protecting individuals’ PII collected, maintained, and processed in all VA information systems, programs, and operations. VA’s privacy policies provide the framework for compliance with laws such as the Privacy Act of 1974, E-Government Act, and other federal mandates, ensuring VA handles PII in a lawful, fair, and transparent manner. All publicly available VA privacy policy documents are available on VA’s Privacy Program: VA Privacy Policies webpage.

5. Privacy Risk Management

VA establishes and uses a multi-level risk management approach that addresses security and privacy risk at the organizational level, the mission/business process level, and the information system level. This is consistent with National Institute of Standards and Technology (NIST) SP 800-139, Managing Information Security Risk: Organization, Mission, and Information System View.

5.1 Implementation of the VA Risk Management Framework

VA follows the principles established in NIST 800-37, Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy. This incorporates security and privacy risk management activities into the system development lifecycle. The SAOP works in coordination with the VA Chief Information Security Officer to:

  • Review and approve the categorization of information systems that create, collect, use, process, store, maintain, disseminate, disclose, or dispose of PII in accordance with Federal Information Processing Standard (FIPS) Publication 199, Standards for Security Categorization of Federal Information and Information Systems, NIST SP 800-122, Guide to Protecting the Confidentiality of Personally Identifiable Information, and NIST SP 800-60, Guide for Mapping Types of Information and Systems to Security Categories.
  • Review authorization packages for information systems that create, collect, use, process, store, maintain, disseminate, disclose, or dispose of PII, to manage privacy risks prior to system authorization.
  • Determine whether additional measures are required to manage privacy risks prior to authorization.

VA maintains an Information Security Knowledge Service which provides enterprise RMF policy and implementation guidance. With the implementation of Rev. 5 NIST SP 800-53, control policy volumes can be found on the Knowledge Service related to VA’s RMF and integration of security and privacy controls.

5.2 Privacy Control Requirements

VA implements NIST SP 800-53 privacy requirements. The SAOP designates which Privacy Controls VA will use as program management, common, system-specific, or hybrid controls.

  • Privacy Program management controls are controls that are generally implemented at the agency level and essential for managing the agency’s privacy program.
  • Multiple information systems inherit common controls.
  • Information system-specific controls are controls that are implemented for a particular information system, or the portion of a hybrid control that is implemented for a particular information system.
  • Hybrid controls are controls that are implemented for an information system in part as a common control and in part as an information system-specific control. The determination as to whether Privacy Control is a common, hybrid, or information system-specific control is based on context.

VA is currently transitioning to NIST SP 800-53 Rev 5 controls. This project plan is being continuously updated and will fully reflect the new controls once the implementation phase is complete. See Appendix B: VA Privacy Controls for the list of control families and controls that VA maintains in their Privacy Overlay.

5.3 Privacy Overlays

The VA Privacy Program leverages privacy overlays established by the Committee on National Security Systems Instruction (CNSSI) No. 1253, Appendix F – Attachment 6 for national security systems as guidance when selecting and assessing effectiveness of privacy protections. An overlay specifies security controls, control enhancements, supplemental guidance, and other supporting information. The purposes of the privacy overlays include providing standard security and privacy control baselines for systems containing PII. Privacy considerations are integrated into the system development life cycle and security processes in the early stages and guide privacy requirements for PHI.

5.4 Privacy Continuous Monitoring (PCM)

The SAOP establishes and maintains a VA-wide Privacy Continuous Monitoring (PCM) Program that implements VA’s PCM Strategy. The design of the PCM Program is to maintain ongoing awareness of threats and vulnerabilities that may pose privacy risks and monitor changes to information systems that process PII. VA conducts privacy control assessments to verify the continued effectiveness of all privacy controls to comply with privacy requirements and manage privacy risks. VA PCM efforts assess programmatic and information system privacy controls across VA Administrations and Staff Offices.

VA Privacy Program Organizational Chart
Table 1:

VA Privacy Assessments that Monitor VA Privacy Controls

6. Requirements for Handling Personally Identifiable Information

6.1 Recognizing PII

SPI is a type of Controlled Unclassified Information (CUI), which includes PII, PHI, and Federal Tax Information (FTI).

  • PII refers to an individual’s information that distinguishes or traces an individual’s identity, alone, or when combined with other identifying information. These include name, Social Security Number (SSN), biometric records, date and place of birth, mother’s maiden name, medical information, personal financial information, credit card account numbers, passport numbers, criminal history, or information that may stigmatize or adversely affect an individual. The term SPI is used interchangeably with PII.
  • PHI, as defined by the HIPAA Privacy Rule, is individually identifiable health information transmitted or maintained in any form or medium by a covered entity, such as VHA. This is another subcategory of PII. Note: VHA uses the term PHI to define information covered by HIPAA but, unlike individually identifiable health information, may or may not be covered by the Privacy Act of 1974 or Title 38 VA Confidentiality Statutes as updated. In addition, PHI excludes employment records held by VHA in its role as an employer.
  • FTI includes tax returns or information about those returns that can come directly from the Internal Revenue Service or other secondary sources like other federal agencies.

6.2 Minimizing the Collection of PII

The Privacy Act of 1974 requires that federal agencies collect only relevant and necessary information about individuals. OMB A-130, Managing Information as a Strategic Resource, directs federal agencies to limit the creation, collection, use, processing, storage, maintenance, dissemination, and disclosure of PII to that which is legally authorized, relevant, and reasonably deemed necessary to properly perform agency functions.

VA maintains an inventory of PII holdings and uses the PTA, PIA and SORN review and approval process to identify reduction opportunities and to ensure, to the maximum extent practicable, that such holding is accurate, relevant, timely, and complete. As part of VA’s commitment to transparency, PIAs and SORNs provide detailed information about the collection, use, and protection of PII. These documents are available for public viewing on the privacy external website at www.va.gov/privacy, enabling the public to understand how their information is managed and safeguarded by VA.

In addition, the VA has established process requirements for justifying the collection, maintenance, and uses of SSNs as directed in VA Directive 6507, Reducing the Use of Social Security Numbers.

6.2.1 Reporting SORNS to OMB and Congress

The intent of the VA Enterprise Social Security Number Reduction (ESSNR) Program is to take steps to reduce and, where possible, eliminate the use of the SSN for uniquely identifying individuals in VA operations, programs, and information systems. VA Enterprise Social Security Number Reduction (ESSNR) Program was originally initiated by OMB Memorandum 07-16, Safeguarding Against and Responding to the Breach of Personally Identifiable Information. Other federal legislation that drives the ESSNR is the Social Security Number Fraud Prevention Act of 2017 and the Consolidated Appropriations Act, 2024, P.L. 118-42, Division A, Title II (Sec. 237).

The Social Security Number Fraud Prevention Act of 2017 restricts the inclusion of SSNs on any document sent by mail. The head of the agency can determine that the SSN inclusion is necessary per the authority of 38 U.S.C. 5101 Final Rule (RIN-2900-AR19), Federal Register: Social Security Number Fraud Prevention Act of 2017 Implementation.

The Consolidated Appropriations Act, 2024, Public Law 118-42 (Division A, Title II, Sec. 237) requires VA to discontinue collecting and using SSNs to authenticate individuals in all VA information systems no later than September 30, 2024. VA may continue to collect and use SSN to identify an individual in accordance with the Privacy Act in an information system if it is necessary to 1) obtain or provide required information from a system that is not under the jurisdiction of the Secretary; 2) comply with a law, regulation, or court order; 3) perform anti-fraud activities; or 4) identify a specific individual where no adequate substitute is available. VA will comply with this legislation through a multi-year phased approach that includes system modifications, user and Veteran re-education and awareness campaigns.

6.3 Handling and Transmitting PII

Handling PII requires strict guidelines due to the sensitivity of the information and the increased risk that compromised information can cause. VA guidance for the handling of PII by VA staff includes:

  • Always store paper documents containing VA-sensitive information securely when not in use.
  • Make sure to clear your work area and secure any documents containing VA-sensitive information before screensharing, turning on video, or leaving the room.
  • When mailing sensitive documents, make sure that the envelopes are addressed correctly and contain only the content intended for that recipient.
  • Before faxing sensitive documents, confirm that the connection is secure, verify the fax number, and ensure that an authorized person is at the receiving end.
  • Store electronic files and documents containing VA-sensitive information on properly secured shared drives.
  • Access only to information, programs, and systems that are needed to perform official duties and never provide access to information to anyone who doesn’t have an authorized need-to-know.
  • Encrypt sensitive PII on computers, email, media, and other devices.
  • Report suspected or identified privacy and security incidents to their supervisor, ISSO, and PO immediately.

7. Privacy Compliance Process

VA Privacy Program works in partnership with program, technical, development, legal, security and privacy teams across VA to assess the privacy risk of VA Information Technology (IT) systems, technologies, pilot projects, rulemakings, web-based developed systems, information collections, programs, and/or projects (collectively referred to as “information systems”). The team works collaboratively to develop mitigation strategies by reviewing and approving all VA privacy compliance documentation. VA’s privacy compliance process is an ongoing cycle with four key parts to ensure appropriate oversight: PTA, PIA, SORN and Periodic Review. Each component plays a role in implementing privacy policies at VA, working collectively to strengthen oversight and increase transparency on activities, while demonstrating accountability to the public.

7.1 Privacy Threshold Analysis

A PTA is an initial privacy assessment used to determine if the information system contains PII and whether a PIA or a SORN is required, and if any other privacy requirements apply to the information system.

VA uses the PTA to:

  • Identify IT systems, programs and projects that have privacy implications.
  • Demonstrate the inclusion of privacy considerations during the review of an IT system, program, project, or boundary.
  • Provide a record of the program, system, or boundary and its privacy requirements.
  • Demonstrate compliance with privacy laws and regulations.

VA requires all VA information systems to complete a PTA to obtain an ATO as a part of VA’s Assessment and Authorization (A&A) process.

7.2 Privacy Impact Assessment

Section 208 of the E-Government Act of 2002 requires all federal agencies to conduct a PIA for all new or substantially changed technology that collects, maintains, or disseminates PII. A PIA is an analysis of how information is handled to ensure handling conforms to applicable legal, regulatory, and policy requirements regarding privacy.

VA uses the PIA to:

  • Determine the risks and effects of collecting, maintaining, and disseminating PII in a system.
  • Examine and evaluate protections and alternative processes for handling information to mitigate potential privacy risks.
  • Demonstrate that program managers and system owners have consciously incorporated privacy protections throughout the development life cycle of a system or program.
  • Provide the public with information about VA’s collection and use of PII.

VA requires all privacy-sensitive information system owners, as determined by the PTA, to complete a PIA to obtain an ATO as a part of VA’s A&A process. A listing of VA PIAs is available at: Privacy Impact Assessments.

7.3 System of Records Notice

VA follows OMB Circular A-108, Federal Agency Responsibilities for Review, Reporting, and Publication under the Privacy Act to meet the requirements for implementing the review, reporting, and publication requirements of the Privacy Act of 1974 and related OMB policies.

The Privacy Act requires agencies to publish a SORN in the Federal Register describing the existence and character of a new or significantly modified system of records (SORs). SORs include any group of records created and maintained by the agency about individuals, which retrieves information by a name or another unique identifier.

A SORN informs the public about what kinds of personal information federal agencies maintain; limits the uses and disclosures of the information to those compatible with the law permitting its collection; and describes how an individual might request access to their information or to seek redress otherwise.

A list of VA published SORNs and related policies is available at: Privacy Act System of Records Notices.

7.3.1 SORN Reviews and Update

VA publishes a SORN in the Federal Register under the following circumstances:

  • When establishing a new SOR.
  • When making significant changes to an existing SOR. A significant change is substantive in nature and warrants a revision of the corresponding SORN to provide notice to the public of the character of the modified SOR. The following are examples of a significant change:
  • Expanding the category of records.
  • Change in the authority for maintenance.
  • New/modified routine use.
  • Promulgation of a rule to exempt a SOR.

VA Privacy Program provides oversight and guidance to the SOR System Managers throughout the development and modification of SORNs. SOR System Managers work with the appropriate parties to publish SORNs for all systems of records. They ensure that procedures for access, correction, or amendment of records conform to VA requirements documented in VA Handbook 6300.5 Procedures for Establishing and Maintaining Privacy Act Systems of Records and follow VA regulations governing Privacy.

7.3.2 Reporting SORNS to OMB and Congress

VA reports all new/modified changes for a SORN to OMB and Congress following the prescribed requirements identified in OMB Circular A-108 Federal Agency Responsibilities for Review, Reporting, and Publication under the Privacy Act. The Privacy Act of 1974 requires each federal department that proposes to establish or significantly modify a SOR to provide adequate advance notice of any such proposal to:

  • OMB
  • Committee on Oversight and Accountability of the U.S. House of Representatives
  • Committee on Homeland Security and Governmental Affairs of the U.S. Senate

VA currently reports the following to Congress:

  • A transmittal letter signed by the SAOP.
  • A narrative statement (this includes a brief overview of the SOR, including an evaluation of the probable or potential effect on the privacy of individuals).
  • A draft of the Federal Register.
  • Any Privacy Act exemption rules.
  • Supplementary documents (as needed).

7.3.3 Privacy Act Statements

When requesting individuals’ information that will become part of a SOR, VA provides a Privacy Act Statement on the form used to collect the information or on a separate form that the individual can retain. VA provides the Privacy Act Statement in compliance with the Paperwork Reduction Act, regardless of whether it is a physical paper or electronic form, on a website, on a mobile application, over the telephone, or through some other medium, collecting the information. This provides sufficient information for the individual to make an informed decision on whether to respond.

The Privacy Act Statement outlines relevant information from the SOR, such as:

  • The authority (whether granted by statute, or by Executive Order of the President) that authorizes soliciting the information, and whether disclosure of such information is mandatory or voluntary.
  • The principal purpose or purposes for the use of the information.
  • The published routine to which the information is subject.
  • The effects on the individual, if any, of not providing all or any part of the requested information.
  • Any appropriate citation (and if possible, a link) to the relevant SORNs.

8. Computer Matching Programs

The Privacy Act of 1974, the Computer Matching and Privacy Protection Act of 1988, and the Payment Integrity Information Act (PIIA) require oversight and approval for VA CMAs. CMAs are between VA and partner agencies or non-federal agencies that allow parties to engage in computer matching programs. A CMP is a computerized comparison of records. The purpose is to establish or verify eligibility or recoup payments for a federal benefit program or relating to federal personnel management. The VA Data Integrity Board (DIB) has oversight and approves all VA CMP activities. Members of the DIB include the SAOP, or CPO, VA Privacy Service Director, Under Secretary for Benefits, Under Secretary for Health, Assistant Secretary for Management, Inspector General, or their designees.

VA publishes CMAs in the Federal Register when VA is the recipient agency for a re-establishment matching program, meaning it restarts a CMA that VA previously held.

The list of published CMAs is available at: Computer Matching Agreements.

8.1 Computer Matching Act – Annual Reporting

The Computer Matching Act and Privacy Protection Act requires VA to implement annual reporting requirements. Under VA Handbook 6502.4, Procedures for Matching Agreements, VA compiles and submits annual reports to Congress and OMB detailing the following:

  • Current information about the composition of the DIB.
  • A list of each matching program in which VA participated during the year.
  • For each matching program for which the DIB waived the requirement for a cost-benefit analysis, and the reasons for the waiver.
  • A description of any matching agreement that the DIB disapproved of and the reasons for the disapproval.
  • A description of any alleged or identified violations of matching agreements and a discussion of any action taken in response.

The DIB’s annual matching activity report may also include a review of any VA matching activities that are not matching programs.

Congress and OMB require VA to provide an advanced notice when a matching program is new, re-established, or significantly modifies a current matching program.

The most recent Computer Matching Activities Report is available at: Computer Matching Activities Report.

9. Privacy Program Operations

VA maintains operational processes and resources to support the effective implementation and management of its agency-wide privacy program. Consistent with applicable privacy requirements and OMB Circular A-130, these activities support the integration of privacy into VA operations and help ensure that privacy risks are appropriately managed. This section describes key operational areas, including privacy workforce management, budget and acquisition, contractor and third-party oversight, privacy awareness and training, and data breach response.

9.1. Privacy Workforce Management

The SAOP assesses and addresses the hiring, training, and professional development needs of the Department with respect to privacy. Additionally, the SAOP who also serves as the VA Chief Information Officer, coordinates with the Chief Human Capital Officer (or Human Resources and Administration (HRA)/Operations, Security, and Preparedness (OSP)) and OIT Chief People Officer to establish and maintain VA’s workforce planning process; assess workforce skills; recruit and retain privacy and IT professionals; develop competency requirements for IT and privacy staff; and ensure managers are aware of flexible hiring authorities.

The SAOP issues Department-wide privacy workforce management policies such as VA Directive 6509, Duties of Privacy Officers, which require VA Executives (e.g., Under Secretaries, Assistant Secretaries, and Other Key Officials) to designate POs at the Administration, Staff Office, and local levels; review skill sets and effectiveness of all POs; assess the adequacy of current privacy staffing levels at all VA facilities; provide the resources necessary to designate POs; and periodically reassess the necessity of additional POs.

The SAOP, in collaboration with the VA CPO and OIT Chief People Officer, facilitates and oversees Department-wide and role-based privacy training for VA’s workforce. This is to ensure VA personnel have the appropriate knowledge and skills to embed privacy into their respective business processes.

This includes:

  • VA Privacy Officer Professionalization Training Program provides POs with resources necessary to support their professional development and privacy education. This includes the VA Privacy Hub which serves as a one-stop shop for VA POs and privacy professionals to quickly and easily access resources to execute their duties; Privacy Webinars and Training on critical and emerging privacy topics; and technical documents and job aids providing instructions on how to complete daily critical tasks and perform privacy assessments of systems and programs.
  • VA Cyber Workforce Program is designed to develop programs for VA to leverage to improve recruitment, retention, development, and growth opportunities for cyber professionals, as defined by the National Initiative for Cybersecurity Education (NICE) Framework. This includes the Career Development Portal, which offers a diverse set of skills-based learning opportunities based on the NICE Work Roles (e.g., Privacy Compliance Manager) in fields of IT, cybersecurity, cross-functional, and artificial intelligence areas.

9.2. Budget and Acquisition

The Program and Acquisition Review Council (PARC) supports OIT in meeting the needs of its business owners through managing, overseeing, and executing the VA IT budget. The PARC also manages the formation and executes core VA portfolios, such as VHA, VBA, NCA, and VA Corporate. The PARC provides a forum for deliberation, and when necessary, escalation to the OIT Governance Board regarding VA’s IT investments needed to achieve VA and OIT mission and business requirements.

The CPO, who serves as an advisor for privacy on the PARC, reviews IT capital investment plans and budgetary requests to ensure that privacy requirements and associated privacy controls, as well as any associated costs, are explicitly identified and included. This is with respect to any IT resources used to create, collect, use, process, store, maintain, disseminate, disclose, or dispose of PII.

9.3. Contractors and Third Parties

VA ensures that contractors, subcontractors, and third-party servicers or associates, and those working on behalf of any of these entities, employ adequate security and privacy controls in accordance with VA directives and handbooks, regulations, guidance, and established service level agreements. The VA Privacy Program coordinates with the Office of Acquisitions, Logistics and Construction to include the applicable privacy clauses in the terms and conditions of contracts and other agreements as outlined in VA Handbook 6500.6, Contract Security.

VA requires Program Managers, Contracting Officer Representatives, POs and ISSOs to complete VA Handbook 6500.6 Contract Security Appendix A Checklist for Information Security in the Initiation Phase of Acquisition at the initiation of IT service acquisitions, statements of work, third-party service agreements, and any other legally binding agreement. The checklist determines what, if any, privacy controls are necessary. This ensures the services, systems, and/or products being procured comply with existing privacy laws and policies regarding the protection, maintenance, dissemination, and disclosure of information.

9.4. Privacy Awareness and Training Program

VA’s Privacy Awareness and Training Program equips the VA workforce with the knowledge and future-ready skills needed to responsibly handle personal information, respond effectively to privacy risks, and comply with information protection laws and regulations. VA Privacy Awareness and Training Programs provide guidance that includes privacy awareness, general and role-based privacy training for employees, contractors, volunteers, and business associates.

9.4.1 Privacy Awareness Training and Rules of Behavior Training

VA Directive 6502, Enterprise Privacy Program, requires all employees, contractors, volunteers, and business associates to complete an initial (within the first 90 days) and an annual mandatory VA Privacy and Information Security Awareness and Rules of Behavior training course and sign VA Information Security Rules of Behavior. VA reviews and updates this mandatory training and Rules of Behavior on an annual and ad-hoc basis to ensure it is consistent with federal and VA policies, standards and guidelines and address new and emerging privacy risks impacting VA and Veterans.

9.4.2 Privacy Role-based Training

VA requires employees and contractors who have significant privacy responsibilities (based on their roles and/or applicable laws governing the information they access) to complete additional advanced mandatory privacy role-based training courses.

These training courses include:

  • Privacy and HIPAA – provides guidance on privacy practices for the use and disclosure of PHI and Veteran rights regarding VHA information. This course is an annual mandatory requirement for employees and contractors with access to PHI and/or VHA computer systems in accordance with VHA Directive 1605.1, Privacy and Release of Information.
  • Information Security and Privacy Role-Based (ISP) Training Courses – provide the requirements, policies, standards, and additional resources concerning information security and privacy controls, consistent with the Federal Information Security Modernization Act (FISMA), NIST guidance, and VA Directive and Handbook 6500, Risk Management Framework for VA Information Systems, VA Information Security Program.
  • Mandatory ISP course for the following roles: Software Developers; Law Enforcement Professionals, Information System Owners; Acquisition Personnel, and Leaders.

9.4.3 Privacy Awareness and Outreach

VA conducts awareness and outreach campaigns and activities to communicate privacy and security resources, products, and techniques to VA employees and contractors. This supports VA ongoing efforts to reduce the number of privacy incidents; shifting behaviors, attitudes, and perspectives of internal stakeholders regarding privacy; and establishing privacy as a priority throughout VA. Outreach campaigns include:

  • Newsletters to VA POs.
  • News and information to employees across VA through articles, informational videos, bulletins, digital signage, and more.
  • Awareness webinars and training on current and trending privacy topics.
  • Host an informative annual event, known as the Privacy Matters Symposium, educating POs on the latest privacy trends and best practices.
  • Articles written specifically for the OIT PO audience, with targeted information that assists them in their daily duties.
  • Safeguard Privacy Campaign, a FY26 initiative, focusing on privacy tips for POs that are shareable to the Veteran community. This campaign includes fact sheets, job aids, articles, a designated webpage and other materials.
  • Training for Success Campaign, a FY26 promotional campaign, on new training courses for POs. These courses are available to all POs and offer educational credits to attendees.

9.5. Data Breach Response

The Data Breach Response Service (DBRS) has the sole responsibility of data breach oversight and management within the VA. DBRS is the lead organization for investigating and adjudicating all Privacy/Security-related incidents involving the potential loss of SPI. The Privacy and Security Events Tracking System (PSETS) is the official system used to record/track/mitigate/close all complaints and incidents that occur at VA.

The DBRS reviews each event in PSETS to validate whether it is either a complaint (unsubstantiated allegation) or an incident. DBRS reviews all incidents in accordance with federal requirements and VA policies and directives to assess the risk of harm to affected individuals. DBRS refers to incidents that involve large numbers of affected individuals, legally complex or multi-jurisdictional incidents, critical high-visibility events of national importance, or incidents that require an elevated level of review across more than one VA administration to the Data Breach Core Team (DBCT) for review. Additionally, incidents that are referred to the DBCT are included in the OIT daily brief to the CIO. For incidents involving missing or stolen equipment, or incidents that have a cybersecurity element, the DBRS alerts and creates a Cybersecurity Events Tracking System (CSETS) event to the Cybersecurity Operations Center (CSOC) as outlined in VA Handbook 6500.2, Management of Breaches Involving Sensitive Personal Information.

9.5.1 Data Breach Core Team

The VA Data Breach Core Team (DBCT) is an elevated, specialized review team that meets weekly at the direction of the CPO and is chaired by the DBRS Director. DBCT membership consists of the entire DBRS staff, CPO, representatives of the Office of General Counsel, VHA Privacy Service, VA Privacy Service, Field Security Service, Office of Congressional and Legislative Affairs, Office of Public and Intergovernmental Affairs, Board of Veterans Appeals, Office of Acquisition and Logistics, and VHA, VBA, NCA, Human Resources Information Service.

The DBCT reviews and adjudicates specific incidents to determine the type of event, impact, breach determination, and any enhanced reporting requirements. DBCT works with the DBRS in analyzing, addressing, and mitigating breaches to ensure timeliness, uniformity, and visibility of VA responses.

9.5.2 Privacy and Security Events Tracking System

Local ISSOs and POs are required to enter all reported complaints and incidents into the PSETS app within one (1) hour of identifying or receiving notification of an incident or complaint. The VA breach management process begins with local ISSOs and POs by gathering information, determining whether a reported event has occurred and completing the local risk assessment as necessary. After completing these steps, the facility level incident response team, in collaboration with the DBRS, conducts further analysis as necessary. The DBRS reviews all entries in the PSETS application daily, evaluates them for clarity and consistency, and adjudicates the official breach determination. Further action may include notification, credit protection, or referral to the DBCT for additional analysis.

9.5.3 Congressional Quarterly Reports on VA Data Breaches

In accordance with the Veterans Benefits, Health Care, and Information Technology Act of 2006 (P.L. 109-461), VA must submit a report on any data breach with respect to the SPI processed or maintained by the Department during the preceding quarter. VA submits the reports to the Committees on Veterans Affairs of the Senate and House of Representatives. Each report submitted includes:

  • Date of Incident and Location of Event.
  • Number of Notification Letters and Credit Protection Letters pending or sent.

The quarterly report to Congress on data incidents for the current fiscal year is available at: Publicly Available Agency Reports on Privacy.

10. Public Resources

10.1 Privacy Workforce Management

VA’s Privacy Program public-facing website at https://www.va.gov/privacy contains information on VA privacy practices such as privacy compliance, safeguarding information, privacy training resources, privacy laws, VA Privacy Principles, policies, and guidance, and contact information. Any privacy questions, concerns, or complaints are addressed by contacting VA Privacy Service at (202) 273-5070 or privacyservice@va.gov.

The VA applies leading privacy practices and adheres to data stewardship principles in managing web user information. The data stewardship principles guiding our efforts include the following goals:

  • Protecting web user privacy
  • Maintaining the confidentiality of web user information
  • Ensuring appropriate levels of security for web user data

VA Web Privacy Policies describe how VA applies these principles to the handling of personal information provided to VA websites and forms. Personal information may include name, email, home, and/or business address; phone numbers; SSN; or other personal identifying information.

Appendix A: Acronyms

Appendix B: VA Privacy Controls

Below are the control families and controls that the VA maintains in their Privacy Overlay.

VA is currently transitioning to the NIST SP 800-53 Revision 5 controls. This project plan is continuously being updated and will fully reflect the new controls once the implementation phase is complete.

Family: Access Control (AC)

Family: Awareness and Training (AT)

Family: Audit and Accountability (AU)

Family: Identification and Authentication (IA)

Family: Incident Response (IR)

Family: Maintenance (MA)

Family: Media Protection (MP)

Family: Physical and Environmental Protection (PE)

Family: Planning (PL)

Family: Program Management (PM)

Family: Processing and Transparency (PT)

Family: Risk Assessment (RA)

Family: System and Services Acquisition (SA)

Family: System and Communications Protection (SC)

Family: System and Information Integrity (SI)

Family: Supply Chain Risk Management (SR)

For more VA Privacy Program information visit https://www.va.gov/privacy.