Free Jun-2024 CTPRP Dumps are Available for Instant Access [Q51-Q69]

Contract addendums are supplementary documents that modify or amend the original contract terms. They can be used to address third party risk obligations, such as security, privacy, compliance, or performance standards, without having to rewrite the entire MSA. However, contract addendums should be consistent with the MSA and clearly specify the scope, duration, and responsibilities of each party. Contract addendums can also be used to update or revise the contract terms in response to changing business needs or regulatory requirements12.
The other statements are true regarding the different types of contracts and agreements between outsourcers and service providers. Evergreen contracts are contracts that do not have a fixed end date and are automatically renewed unless one party decides to terminate them under the existing contract provisions3.
RFPs are documents that solicit proposals from potential service providers for a specific project or service.
RFPs should include mandatory requirements based on an organization’s TPRM program policies, standards and procedures, such as risk assessment, due diligence, monitoring, reporting, and remediation . SOWs are documents that define the operational requirements and obligations for each party, such as the scope, deliverables, timelines, costs, quality, and performance metrics . References:
* 1: Contracts and third-party risk – KPMG UK
* 2: Third-Party Risk & Contract Management: A Comprehensive Beginner’s Guide – Trackado
* 3: What Is an Evergreen Contract? | Legal Beagle
* : [Best Practices Guidance for Third Party Risk – GARP]
* : Third-Party Risk Management: A Comprehensive Guide – UpGuard
* : Statement of Work (SOW) – Definition, Contents & Examples
* : How to Write a Statement of Work for Any Industry | Smartsheet

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

Personally identifiable information (PII) is any data that can be used to identify, contact, or locate an individual, such as name, address, email, phone number, social security number, etc. PII is subject to various legal and regulatory requirements, such as the GDPR, HIPAA, PCI DSS, and others, depending on the industry and jurisdiction. PII also poses significant security and privacy risks, as it can be exploited by malicious actors for identity theft, fraud, phishing, or other cyberattacks. Therefore, organizations that collect, store, process, or transmit PII must implement appropriate safeguards to protect it from unauthorized access, disclosure, modification, or loss.
One of the key safeguards for PII protection is encryption, which is the process of transforming data into an unreadable format using a secret key. Encryption ensures that only authorized parties who have the key can access the original data. Encryption can be applied to data at rest (stored on a device or a server) or data in transit (moving across a network or the internet). Encryption can also be symmetric (using the same key for encryption and decryption) or asymmetric (using a public key for encryption and a private key for decryption).
Another key safeguard for PII protection is authentication, which is the process of verifying the identity of a user or a system that requests access to data. Authentication ensures that only legitimate and authorized parties can access the data. Authentication can be based on something the user knows (such as a password or a PIN), something the user has (such as a token or a smart card), something the user is (such as a fingerprint or a face scan), or a combination of these factors. Authentication can also be enhanced by using additional methods, such as one-time passwords, challenge-response questions, or multi-factor authentication.
When defining third party requirements for transmitting PII, the factors that provide stronger controls are the strength of encryption cipher and authentication method. These factors determine how secure and reliable the data transmission is, and how resistant it is to potential attacks or breaches. The strength of encryption cipher refers to the algorithm and the key size used to encrypt the data. The stronger the cipher, the more difficult it is to break or crack the encryption. The strength of authentication method refers to the type and the number of factors used to verify the identity of the user or the system. The stronger the authentication method, the more difficult it is to impersonate or compromise the user or the system.
The other factors, such as full disk encryption and backup, available bandwidth and redundancy, and logging and monitoring, are also important for PII protection, but they do not directly affect the data transmission process. Full disk encryption and backup are relevant for data at rest, not data in transit. They provide protection in case of device theft, loss, or damage, but they do not prevent data interception or modification during transmission. Available bandwidth and redundancy are relevant for data availability and performance, not data security and privacy. They ensure that the data transmission is fast and reliable, but they do not prevent data exposure or corruption during transmission. Logging and monitoring are relevant for data audit and compliance, not data encryption and authentication. They provide visibility and accountability for the data transmission activities, but they do not prevent data access or misuse during transmission. References:
* : What is Data Encryption? | Definition and Examples | Imperva
* : What is Authentication? | Definition and Examples | Imperva
* : Personally Identifiable Information (PII) – Imperva
* : Data Protection – Shared Assessments

Remote access is any connection made to an organization’s internal network and systems from an external source by a device or host. Remote access can enable greater worker flexibility and productivity, but it also poses significant security risks, such as unauthorized access, data leakage, malware infection, or network compromise. Therefore, it is important to evaluate a third party’s use of remote access within their information security policy, which should define the roles, responsibilities, standards, and procedures for remote access.
One of the key components of evaluating a third party’s use of remote access within their information security policy is identifying the use of multifactor authentication. Multifactor authentication is a method of verifying the identity of a remote user by requiring two or more factors, such as something the user knows (e.g., password, PIN), something the user has (e.g., token, smart card), or something the user is (e.g., fingerprint, face). Multifactor authentication enhances the security of remote access by making it harder for attackers to impersonate or compromise legitimate users. According to the NIST Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security1, multifactor authentication should be used for all remote access, especially for high-risk situations, such as accessing sensitive data or privileged accounts.
The other options are not components of evaluating a third party’s use of remote access within their information security policy. Maintaining blocked IP address ranges, reviewing the testing and deployment procedures to networking components, and providing guidelines to configuring ports on a router are all examples of network security controls, but they are not specific to remote access. They may be part of the overall information security policy, but they are not sufficient to assess the security of remote access.
References:
* NIST Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security
* How to Implement an Effective Remote Access Policy
* Why Managing Third-Party Access Requires A Better Approach

A Zero Trust approach to access management is based on the principle of verifying every access request as if it originates from an open network, regardless of the source, destination, or context. This means that no implicit trust is granted based on network location, user identity, or device status. Instead, every access request is evaluated based on multiple factors, such as user credentials, device health, data sensitivity, and threat intelligence. A Zero Trust approach also requires that all communication is encrypted and protected, and that access is granted on a per session basis with the least privilege principle123.
Utilizing a solution that allows direct access by third parties to the organization’s network does not reflect a Zero Trust approach, because it implies that the network perimeter is a reliable boundary for security and trust.
This assumption is risky, because it exposes the organization to potential breaches and attacks from compromised or malicious third parties, who may have access to sensitive data and resources without proper verification or protection. A Zero Trust approach would require that third parties use secure and isolated channels to access the organization’s network, such as VPNs, proxies, or gateways, and that their access is monitored and controlled based on granular policies and conditions123. References:
* Zero Trust part 1: Identity and access management
* Zero Trust Model – Modern Security Architecture | Microsoft Security
* Zero Trust identity and access management development best practices …

External continuous monitoring solutions are tools or services that provide objective and timely data on the cybersecurity posture and performance of third-party vendors. They typically include components such as:
* Status updates on localized events based on geolocation, which can alert the organization to potential disruptions or incidents affecting the vendor’s operations or infrastructure in a specific region or country12.
* Alerts on legal and regulatory actions involving the vendor, which can indicate the vendor’s compliance status, reputation, or liability exposure13.
* Reports that identify changes in vendor financial viability, which can signal the vendor’s ability to
* sustain its business operations, invest in security, or honor its contractual obligations14.
However, metrics that track SLAs for performance management are not typically included in external continuous monitoring solutions, as they are more relevant for internal monitoring and reporting. SLAs are service level agreements that define the expected quality, availability, and reliability of the vendor’s services or products, as well as the penalties or remedies for non-compliance. SLAs are usually measured and reported by the vendor itself, or by a third-party auditor or assessor, based on the specific criteria and frequency agreed upon by the parties . Therefore, option C is the correct answer. References:
* Third Party Risk Management Framework, Module 5: Program Implementation, Section 5.2: Ongoing Monitoring, p. 32
* Bitsight Continuous Monitoring, Section: Uncover hidden risks
* Best-Practices Guidance for Third-Party Risk, Section: Monitor Third-Party Compliance with Regulations and Standards, p. 3
* Five Best Practices to Manage and Control Third-Party Risk, Section: Monitor Third-Party Financial Health, p. 4
* [Third Party Risk Management Framework], Module 4: Program Components, Section 4.3: Contracting, p. 24
* [A Better Way to Manage Third-Party Risk], Section: Establish clear service level agreements (SLAs) and key performance indicators (KPIs), p. 2

Multi-factor authentication (MFA) is an electronic authentication method that requires a user to present two or more pieces of evidence (or factors) to an authentication mechanism. The factors can be something the user knows (such as a password or a PIN), something the user has (such as a smartphone or a security token), or something the user is (such as a fingerprint or a facial recognition). MFA enhances the security of online accounts and applications by making it harder for attackers to gain access with stolen or guessed credentials.
MFA is recommended as a best practice for third-party risk management, as it can reduce the risk of unauthorized access, data breaches, and identity theft. MFA is also a requirement for some regulatory standards and frameworks, such as PCI DSS, HIPAA, and NIST 800-63. References:
* What is: Multifactor Authentication
* Set up your Microsoft 365 sign-in for multi-factor authentication
* Multi-factor authentication – Wikipedia
* Shared Assessments CTPRP Study Guide, page 19
* Shared Assessments CTPRP Job Guide, page 14
* Best Practices Guidance for Third Party Risk, page 9

Third-party risk management (TPRM) is the process of identifying, assessing, and mitigating the risks associated with outsourcing business activities or functions to external entities. TPRM is influenced by various regulations that aim to protect the interests of customers, stakeholders, and regulators from the potential harm caused by third-party failures or misconduct. These regulations may vary depending on the industry, jurisdiction, and nature of the third-party relationship. Therefore, it is important for organizations to update their inventory of regulations that impact their TPRM program during their annual risk assessment, and prioritize the regulations that are most relevant and critical for their business objectives and risk appetite.
The optimal approach to prioritizing the regulations is to identify the applicable regulations that require an extension of specific obligations to service providers. This means that the organization should focus on the regulations that impose certain requirements or expectations on the organization and its third-party partners, such as data protection, security, compliance, reporting, auditing, or performance standards. These regulations may also specify the roles and responsibilities of the organization and the service provider, the scope and frequency of due diligence and monitoring activities, the contractual clauses and terms, and the remediation and termination procedures. By identifying these regulations, the organization can ensure that its TPRM program is aligned with the regulatory expectations and obligations, and that it can effectively manage and mitigate the risks associated with its third-party relationships.
Some examples of regulations that require an extension of specific obligations to service providers are:
* The General Data Protection Regulation (GDPR): This is a European Union regulation that governs the collection, processing, and transfer of personal data of individuals in the EU. The GDPR requires organizations to implement appropriate technical and organizational measures to protect the personal data, and to only engage with service providers that can provide sufficient guarantees of data protection.
The GDPR also requires organizations to enter into written contracts with their service providers that specify the subject matter, duration, nature, and purpose of the data processing, as well as the rights and obligations of both parties. The GDPR also imposes strict notification and reporting requirements in case of data breaches or violations.
* The Health Insurance Portability and Accountability Act (HIPAA): This is a US federal law that regulates the privacy and security of health information of individuals. The HIPAA requires covered entities, such as health care providers, health plans, and health care clearinghouses, to safeguard the health information of their patients, and to only disclose or share it with authorized parties. The HIPAA also requires covered entities to enter into business associate agreements with their service providers that handle or access the health information on their behalf. These agreements must specify the permitted and required uses and disclosures of the health information, the safeguards and measures to protect the health information, and the reporting and notification obligations in case of breaches or incidents.
* The Sarbanes-Oxley Act (SOX): This is a US federal law that aims to improve the accuracy and reliability of corporate financial reporting and disclosure. The SOX requires public companies to establish and maintain internal controls over their financial reporting processes, and to assess and report on the effectiveness of these controls. The SOX also requires public companies to ensure that their external auditors are independent and qualified, and to disclose any material weaknesses or deficiencies in their internal controls. The SOX also applies to the service providers that perform or support the financial reporting functions of the public companies, such as accounting firms, information technology vendors, or consultants. The SOX requires public companies to evaluate and monitor the internal controls of their service providers, and to include them in their scope of audit and reporting.
References:
* Third-Party Risk Management and Mitigation | Gartner
* Best Practices to Jumpstart Third-Party Risk Management Program
* Third-party risk management best practices and why they matter
* GDPR and Third-Party Risk Management
* HIPAA Compliance for Business Associates and Third-Party Service Providers
* SOX Compliance Requirements for Third-Party Service Providers

Data Loss Prevention (DLP) programs are not based on default tool configuration, but on the specific needs and risks of the organization. DLP programs should be tailored to the data types, locations, flows, and users that are relevant to the business. DLP programs should also align with the regulatory and contractual obligations, as well as the data risk appetite, of the organization. Default tool configuration may not adequately address these factors and may result in either over-blocking or under-protecting data. Therefore, statement C is false about DLP programs. References:
* 1: The Best Data Loss Prevention Software Tools – Comparitech
* 2: Build a Successful Data Loss Prevention Program in 5 Steps – Gartner
* 3: What is data loss prevention (DLP)? | Microsoft Security

Hybrid cloud is the cloud deployment model that is primarily used for load balancing. Load balancing is the process of distributing workloads and network traffic across multiple servers or resources to optimize performance, reliability, and scalability1. Load balancing can help prevent overloading or underutilizing any single server or resource, as well as improve fault tolerance and availability. Hybrid cloud is a mix of two or more different deployment models, such as public cloud, private cloud, or community cloud2. Hybrid cloud allows organizations to leverage the benefits of both public and private clouds, such as cost efficiency, scalability, security, and control3. Hybrid cloud can also enable load balancing across different cloud environments, depending on the demand, cost, and performance requirements of each workload. For example, an organization can use a private cloud for sensitive or mission-critical applications that require high security and performance, and a public cloud for less sensitive or variable applications that require more scalability and flexibility. By using a hybrid cloud, the organization can balance the load between the private and public clouds, and optimize the resource utilization and cost efficiency of each cloud.
The other cloud deployment models are not primarily used for load balancing, although they may have some load balancing capabilities within their own environments. Public cloud is the infrastructure that is shared by multiple tenants and open to the public. Anyone can use the public cloud by subscribing to it. Public cloud offers high scalability, elasticity, and cost-effectiveness, but may have lower security, privacy, and control than private cloud2. Community cloud is the infrastructure that is shared by similar consumers who collaborate to set up a cloud for their exclusive use. For example, government organizations can form a cloud for their exclusive use. Community cloud offers some benefits of both public and private clouds, such as shared costs, common standards, and enhanced security, but may have lower scalability and flexibility than public cloud2. Private cloud is the infrastructure that is for the exclusive use of a single organization. The cloud may or may not be operated by the organization. Private cloud offers high security, privacy, and control, but may have lower scalability, elasticity, and cost-effectiveness than public cloud2. References:
* 1: What is Load Balancing? | How Load Balancing Works | F5
* 2: The NIST Definition of Cloud Computing
* 3: What is Hybrid Cloud? | IBM
* : Hybrid Cloud Load Balancing – Kemp Technologies
* : [Hybrid Cloud Load Balancing: What You Need to Know – CloudHealth by VMware]

According to the Shared Assessments Certified Third Party Risk Professional (CTPRP) Study Guide, the third party risk assessor’s role is to evaluate the design and operating effectiveness of the third party’s controls based on an industry framework, such as ISO, NIST, COBIT, or COSO1. The assessor’s role is not to provide an opinion on the effectiveness of controls, but rather to report the results of the evaluation in a factual and objective manner2. The assessor’s role is also to conduct discovery with subject matter experts to understand the control environment, to conduct discovery and validate responses from the risk assessment questionnaire by testing or validating controls, and to review compliance artifacts and identify potential control gaps based on evaluation of the presence of control attributes1. These are all true statements that describe the assessor’s role when conducting a controls evaluation using an industry framework.
References:
* 1: Shared Assessments Certified Third Party Risk Professional (CTPRP) Study Guide, page 29
* 2: What is a Third-Party Risk Assessment? – RiskOptics

A regulation is a rule of order having the force of law, prescribed by a superior or competent authority, relating to the actions of those under the authority’s control. Regulations are issued by various government departments and agencies to carry out the intent of legislation enacted by the legislature of the applicable jurisdiction. Regulations also function to ensure uniform application of the law. A standard is a guideline established generally by private-sector bodies and that are available for use by any person or organization, private or government. The term includes what are commonly referred to as ‘industry standards’ as well as
‘consensus standards’. Standards are developed through a voluntary process of collaboration and consensus among stakeholders, such as manufacturers, consumers, regulators, and experts. Standards may reflect best practices, technical specifications, performance criteria, or quality requirements. Standards do not have the force of law unless they are adopted or referenced by a regulation. Therefore, a regulation must be adhered to by all companies subject to its requirements, but companies can voluntarily choose to follow standards that are relevant and beneficial to their operations, products, or services. References:
* The Difference Between Regulations and Standards
* Regulations vs Standards: Clearing Up the Confusion – AEM
* Standards vs. Regulations
* Certified Third Party Risk Professional (CTPRP) Study Guide

The scenario described indicates a lack in the vendor’s Asset Management Program. An effective Asset Management Program includes maintaining an accurate inventory of hardware and devices, monitoring their status, and promptly identifying and responding to any losses or discrepancies. The failure to discover the loss of laptops and a tablet that processed company data for two years suggests deficiencies in tracking and managing physical assets. This lapse can lead to risks associated with data security, regulatory compliance, and operational integrity. A robust Asset Management Program should ensure that all assets are accounted for, their usage is monitored, and any anomalies or losses are quickly identified and addressed.
References:
* IT asset management standards, such as ISO/IEC 27001 (Information Security Management), emphasize the importance of maintaining an inventory of assets and implementing appropriate controls to safeguard
* organizational assets.
* The “IT Asset Management Handbook” by the International Association of IT Asset Managers (IAITAM) provides guidelines on establishing a comprehensive Asset Management Program, including best practices for asset tracking, monitoring, and loss prevention.

In patch management, testing is the most crucial factor when conducting post-cybersecurity incident analysis related to systems and applications. Proper testing of patches before deployment ensures that they effectively address vulnerabilities without introducing new issues or incompatibilities that could impact system functionality or security. Testing allows organizations to verify that the patch resolves the identified security issue without adversely affecting the system or application’s performance. It also helps in identifying potential conflicts with existing configurations or dependencies. Effective testing strategies include regression testing, performance testing, and security testing to ensure comprehensive validation of the patch’s effectiveness and safety before widespread deployment. This approach aligns with best practices in patch management, emphasizing the importance of thorough testing to mitigate the risk of unintended consequences and ensure the continued security and stability of systems and applications.
References:
* Industry standards such as ISO/IEC 27001 (Information Security Management) highlight the importance of a systematic approach to managing patches, including the role of testing in assessing the effectiveness and impact of patches.
* Resources like “Patch Management Best Practices” from the Center for Internet Security (CIS) provide guidance on developing and implementing a patch management program that includes rigorous testing procedures to ensure patches are safely and effectively applied.

The purpose of internal communications and information sharing using TPRM performance metrics is to inform and align the organization’s stakeholders on the status, progress, and outcomes of the TPRM program.
This includes communicating the results of vendor assessments, the compliance level of the organization’s policies and procedures, and the periodic reporting to management and other relevant parties. However, documenting the corrective action plan between external parties is not an internal communication, but rather an external one. This is because the corrective action plan is a formal agreement between the organization and the vendor to address and resolve the issues identified in the assessment. Therefore, this statement is not an example of the purpose of internal communications and information sharing using TPRM performance metrics. References:
* 15 KPIs & Metrics to Measure the Success of Your TPRM Program
* Third-party risk management metrics: Best practices to enhance your program
* 3 Best Third-Party Risk Management Software Solutions (2024)

One of the key elements of a robust information security policy is the definition and implementation of requirements for third party governance and oversight. This means that the vendor should have clear and consistent processes and procedures for managing and monitoring the information security risks and controls of their subcontractors, suppliers, or service providers. Third party governance and oversight should include the following aspects12:
* Establishing criteria and standards for selecting and evaluating third parties based on their information security capabilities and performance
* Conducting regular and comprehensive assessments and audits of third parties’ information security policies, practices, and incidents
* Ensuring contractual agreements and service level agreements (SLAs) with third parties include information security clauses and obligations
* Maintaining visibility and communication with third parties regarding their information security status and issues
* Implementing corrective actions and remediation plans for any identified information security gaps or weaknesses
* Terminating or suspending the relationship with third parties that fail to meet the information security expectations or requirements If a vendor’s response does not specify any requirements for third party governance and oversight, it should trigger further investigation of their information security policies.
This indicates that the vendor may not have a comprehensive and effective approach to managing the information security risks and impacts of their extended network of partners. This could expose the vendor and their clients to potential data breaches, cyberattacks, compliance violations, or reputational
* damages. Therefore, the vendor should be asked to provide more details and evidence of how they ensure the information security of their third parties, and how they address any information security incidents or issues involving their third parties. References:
* 1: Third-Party Information Security Risk Management Policy – SecurityStudio
* 2: Ensuring Data Protection for Third Parties: Best Practices | UpGuard Blog

According to the Shared Assessments Certified Third Party Risk Professional (CTPRP) Study Guide, data loss prevention (DLP) is a strategy for preventing the unauthorized disclosure, transfer, or misuse of sensitive data, such as personally identifiable information (PII), personal health information (PHI), or intellectual property (IP)1. Endpoint security is a component of DLP that focuses on protecting the devices (such as laptops, tablets, or smartphones) that access and store sensitive data from internal or external threats2. Therefore, data loss prevention in endpoint security is the strategy for preventing exfiltration of confidential information by users who access company systems, as this could result in data breaches, regulatory fines, reputational damage, or competitive disadvantage3.
The other options are not the best descriptions of data loss prevention in endpoint security, as they either relate to different aspects of data protection or security, or do not address the specific goal of preventing data exfiltration. Data backups are a strategy for ensuring data recovery in the event of a disaster, but they do not prevent data loss or leakage from unauthorized access or transfer. High-availability is a strategy for ensuring data availability and continuity, but it does not prevent data loss or leakage from malicious or accidental actions. Malware prevention is a strategy for ensuring data integrity and confidentiality, but it does not prevent data loss or leakage from legitimate users who may misuse or overshare data.
References:
* 1: Shared Assessments Certified Third Party Risk Professional (CTPRP) Study Guide, page 25
* 2: What is Endpoint Security? | McAfee
* 3: What is data loss prevention (DLP)? | Microsoft Security
* [4]: Data Backup vs. Data Recovery: What’s the Difference? | Carbonite
* [5]: What is High Availability? | IBM
* [6]: What is Malware? | Norton

Notification obligations in incident response are the legal or contractual duties to inform relevant parties about a security breach or incident that affects their data or systems. These obligations may vary depending on the type, scope, and impact of the incident, as well as the jurisdiction, industry, and contractual agreements involved. The factors that are most likely to trigger notification obligations are:
* Regulatory requirements: Different laws and regulations may impose different notification obligations on organizations that experience or cause a security incident. For example, the General Data Protection Regulation (GDPR) requires data controllers to notify the supervisory authority within 72 hours of becoming aware of a personal data breach, and to notify the affected data subjects without undue delay if the breach poses a high risk to their rights and freedoms1. Similarly, the Computer-Security Incident Notification Rule requires banks and their service providers to notify their primary federal regulator as soon as possible, but no later than 36 hours, after a computer-security incident that materially disrupts, degrades, or impairs their operations, services, or customers2.
* Data classification or sensitivity: The type and sensitivity of the data involved in a security incident may also affect the notification obligations. For example, if the data contains personally identifiable information (PII), health information, financial information, or other confidential or sensitive information, the organization may have to notify the data owners, regulators, law enforcement, or other stakeholders about the incident and the potential risks to their privacy or security3. The data classification or sensitivity may also determine the content and timing of the notification, as well as the appropriate communication channels to use.
* Contractual terms: The contractual agreements between an organization and its third-party vendors or service providers may also specify the notification obligations in case of a security incident. For example, the contract may define the roles and responsibilities of each party, the notification procedures and timelines, the information to be shared, the remediation actions to be taken, and the penalties or liabilities for breach of contract. The contractual terms may also reflect the regulatory requirements or industry standards that apply to the organization or the third party.
The factor that is least likely to trigger notification obligations is:
* Encryption of data: Encryption of data is a security measure that protects the data from unauthorized access, modification, or disclosure. Encryption of data may reduce the impact or severity of a security incident, as it may prevent or limit the exposure of the data to malicious actors. However, encryption of data does not eliminate the notification obligations, as the organization still has to assess the nature and extent of the incident, and determine whether the encryption was effective or compromised. Moreover, encryption of data may not be sufficient to protect the data from other types of threats, such as deletion, corruption, or ransomware. Therefore, encryption of data is not a factor that influences the notification obligations in incident response.
References:
* 1: GDPR Article 33: Notification of a personal data breach to the supervisory authority
* 2: Computer-Security Incident Notification Rule
* 3: Third-Party Incident Management (TPIM): How to Balance IRPs with Third Parties
* : [Improving Third-Party Incident Response]
* : [Third-Party Incident Response Playbook]
* : [Does Encryption Protect You From a Data Breach?]

Shadow IT is the use and management of any IT technologies, solutions, services, projects, and infrastructure without formal approval and support of internal IT departments. Shadow IT can pose significant security risks to the organization, such as data breaches, compliance violations, malware infections, or network disruptions.
Therefore, assessing and mitigating the risk of shadow IT is an essential part of organizational security.
One of the most important factors when assessing the risk of shadow IT is whether the organization maintains adequate policies and procedures that communicate required controls for security functions. Policies and procedures are the documents that define the organization’s security objectives, standards, roles, responsibilities, and processes. They provide guidance and direction for the organization’s security activities, such as risk assessment, vendor management, incident response, data protection, access control, etc. They also establish the expectations and requirements for the organization’s employees, vendors, and other stakeholders regarding the use and management of IT resources.
By maintaining adequate policies and procedures that communicate required controls for security functions, the organization can:
* Educate and inform its employees about the security risks and implications of shadow IT, and the benefits and advantages of using authorized and supported IT resources.
* Establish and enforce clear and consistent rules and boundaries for the use and management of IT resources, and the consequences and penalties for violating them.
* Monitor and audit the compliance and performance of its employees, vendors, and other stakeholders regarding the use and management of IT resources, and identify and address any deviations or issues.
* Review and update its policies and procedures regularly, and communicate any changes or updates to its employees, vendors, and other stakeholders.
By doing so, the organization can reduce the likelihood and impact of shadow IT, and increase the visibility and accountability of its IT environment. The organization can also foster a culture of security awareness and responsibility among its employees, vendors, and other stakeholders, and encourage them to report and resolve any shadow IT incidents or problems.
The other factors, such as the organization’s security training and certification, staffing levels, and resources and investment, are also relevant for assessing the risk of shadow IT, but they are not as important as the organization’s policies and procedures. Security training and certification can help the organization’s security personnel to acquire and maintain the necessary skills and knowledge to deal with shadow IT, but they do not address the root causes or motivations of shadow IT. Staffing levels can affect the organization’s ability to detect and respond to shadow IT, but they do not prevent or deter shadow IT from occurring. Resources and investment can enable the organization to provide adequate and appropriate IT resources to its employees, vendors, and other stakeholders, but they do not guarantee the satisfaction or compliance of those parties.
References:
* : Shadow IT Explained: Risks & Opportunities – BMC Software
* : What is Shadow IT? | IBM
* : Shadow IT: What Are the Risks and How Can You Mitigate Them? – Ekran System
* : Policies and Procedures – Shared Assessments