A risk register is a tool that records and tracks the identified risks, their probability, impact, status, and mitigation actions throughout the life cycle of a third-party relationship1. A risk register typically includes the following components2:
* A unique identifier for each risk
* A description of the risk and its source
* A rating or grading of the risk according to a risk assessment table or hierarchy
* An assessment of the impact and likelihood the risk will occur and the possible seriousness
* An outline of proposed mitigation actions and assignment of risk owner
* A status update on the risk and the progress of the mitigation actions
* A target date for resolving the risk or closing the action A vendor inventory is a list of all the third parties that a banking organization engages with, along with relevant information such as the type, scope, and nature of the services provided, the contract terms and conditions, the performance indicators, and the risk ratings3. A vendor inventory is not a component of a risk register, but rather a separate document that supports the planning and due diligence phases of the third-party relationship life cycle. A vendor inventory may be prioritized by contract value, but also by other criteria such as the criticality of the service, the risk level of the vendor, and the strategic importance of the relationship.
References:
* 1: Third-Party Risk Management (TPRM): Final Interagency Guidance, KPMG, June 2023
* 2: What Is Third-Party Risk Management (TPRM)? 2024 Guide, UpGuard, January 2024
* 3: Third-Party Risk Management Guidance, OCC Bulletin 2023-29, October 2023
* [4]: Certified Third Party Risk Professional (CTPRP) Study Guide, Shared Assessments, 2023
* [5]: Best Practices Guidance for Third-Party Risk, GARP, February 2023

Physical access procedures and activity logs are important components of third-party risk management, as they help to ensure the security and integrity of the physical assets and data of the organization and its third parties.
However, requiring physical access logs to be retained indefinitely for audit purposes is not a best practice, as it may pose legal, regulatory, and operational challenges. According to the Supplemental Examination Procedures for Risk Management of Third-Party Relationships, physical access logs should be retained for a reasonable period of time, consistent with the organization's policies and procedures, and in compliance with applicable laws and regulations1. Retaining physical access logs indefinitely may increase the risk of unauthorized access, data breaches, privacy violations, and litigation2. Therefore, the statement B is the correct answer, as it is the only one that does not reflect a best practice for physical access procedures and activity logs.
References:
* 1: How to Write Third-Party Risk Management (TPRM) Policies and Procedures - SecurityScorecard Blog
* 2: Five Best Practices to Manage and Control Third-Party Risk - Broadcom Inc.
* 3: A checklist for third-party risk management platforms - Crowe LLP
* 4: Supplemental Examination Procedures for Risk Management of Third-Party Relationships
* 5: Third Party Risk Management: Why It's Important And What Features To Look For - Expert Insights

Web content accessibility guidelines (WCAG) are a set of standards that aim to make web content more accessible to people with disabilities, such as visual, auditory, cognitive, or motor impairments. While WCAG is a good practice for web development and usability, it is not directly related to web application security.
WCAG does not address the common security risks that web applications face, such as injection, broken authentication, misconfiguration, or vulnerable components. Therefore, adhering to WCAG is not a method of securing web applications, unlike the other options. References:
* 4: OWASP Top 10, a standard awareness document for web application security, lists the most critical security risks to web applications and provides best practices to prevent or mitigate them.
* 5: SANS Institute, a leading provider of cybersecurity training and certification, offers a security checklist for web application technologies (SWAT) that covers best practices for error handling, data protection, configuration, authentication, session management, input and output handling, and access control.
* 6: Built In, a platform for tech professionals, provides 13 web application security best practices, such as using a web application firewall, keeping track of APIs, enforcing expected application behaviors, and following the OWASP Top 10.

In IT asset end-of-life (EOL) processes, the requirement to conduct periodic risk assessments specifically to determine end-of-life is not typically included. EOL processes generally focus on managing the decommissioning and secure disposal of IT assets that have reached the end of their useful life or support period. This includes tracking the status of assets, managing updates and support for third-party systems and applications, and establishing procedures for the secure destruction of assets at sunset. While risk assessments are crucial in overall IT asset management, they are not usually a direct component of determining an asset's EOL status, which is more often based on operational effectiveness, manufacturer support, and technological obsolescence.
References:
* IT asset management and disposal best practices, such as those outlined in the NIST Guidelines for Media Sanitization (NIST SP 800-88), focus on the secure and environmentally responsible disposal of IT assets without specifically mandating periodic risk assessments for EOL determination.
* The "IT Asset Disposal (ITAD) Best Practice Guide" by the International Association of IT Asset Managers (IAITAM) provides insights into effective EOL processes, including tracking, updating, and securely destroying IT assets.

The best approach to address the conflict between the vendor's legal obligations to retain data for tax purposes and the company's policy to require data return or destruction at contract termination is A. Determine if a policy exception and approval is required, and require that data safeguarding obligations continue after termination. This approach recognizes that the vendor may have valid reasons to retain some data for a certain period of time, and that the company may have flexibility to grant exceptions to its policy under certain circumstances. However, this approach also ensures that the company maintains oversight and control over the data that the vendor retains, and that the vendor continues to comply with the data safeguarding obligations, such as encryption, access control, audit, and breach notification, until the data is returned or destroyed. This approach balances the interests and risks of both parties, and minimizes the potential for data breaches, misuse, or loss.
The other approaches are not the best ways to address the conflict, as they may create more problems or risks for either party. B. Change the risk rating of the vendor to reflect a higher risk tier. This approach does not resolve the conflict, but rather shifts the responsibility to the company to manage the increased risk of the vendor retaining the data. Changing the risk rating may also affect the contract terms, such as pricing, service level agreements, or liability clauses, and may require renegotiation or termination of the contract. C. Insist the vendor adheres to the policy and contract provisions without exception. This approach is too rigid and may not be feasible or reasonable for the vendor, especially if they have legal obligations to retain the data. This approach may also damage the relationship and trust between the parties, and may lead to disputes or litigation. D. Conduct an assessment of the vendor's data governance and records management program. This approach is too time-consuming and costly, and may not be necessary or relevant for the conflict. Conducting an assessment may provide some assurance about the vendor's data practices, but it does not address the underlying issue of the conflicting data retention requirements. Moreover, conducting an assessment may not be possible or appropriate during the contract negotiation process, as it may require access to the vendor's systems, data, or personnel. References:
* : Best Practices for Data Destruction - ed
* : CHALLENGES AND RISKS INVOLVED WITH DATA RETENTION - DataOlogie
* : Third-Party Risk Management: Final Interagency Guidance
* : Ensuring Data Protection for Third Parties: Best Practices | UpGuard Blog