PECB ISO-IEC-27005 Risk Manager Practice Exams
Last updated on Oct 21,2026- Exam Code: ISO-IEC-27005 Risk Manager
- Exam Name: PECB Certified ISO/IEC 27005 Risk Manager
- Certification Provider: PECB
- Latest update: Oct 21,2026
Scenario 3: Printary is an American company that offers digital printing services. Creating cost-effective and creative products, the company has been part of the printing industry for more than 30 years. Three years ago, the company started to operate online, providing greater flexibility for its clients. Through the website, clients could find information about all services offered by Printary and order personalized products. However, operating online increased the risk of cyber threats, consequently, impacting the business functions of the company. Thus, along with the decision of creating an online business, the company focused on managing information security risks. Their risk management program was established based on ISO/IEC 27005 guidelines and industry best practices.
Last year, the company considered the integration of an online payment system on its website in order to provide more flexibility and transparency to customers. Printary analyzed various available solutions and selected Pay0, a payment processing solution that allows any company to easily collect payments on their website. Before making the decision, Printary conducted a risk assessment to identify and analyze information security risks associated with the software. The risk assessment process involved three phases: identification, analysis, and evaluation. During risk identification, the company inspected assets, threats, and vulnerabilities. In addition, to identify the information security risks, Printary used a list of the identified events that could negatively affect the achievement of information security objectives. The risk identification phase highlighted two main threats associated with the online payment system: error in use and data corruption After conducting a gap analysis, the company concluded that the existing security controls were sufficient to mitigate the threat of data corruption. However, the user interface of the payment solution was complicated, which could increase the risk associated with user errors, and, as a result, impact data integrity and confidentiality.
Subsequently, the risk identification results were analyzed. The company conducted risk analysis in order to understand the nature of the identified risks. They decided to use a quantitative risk analysis methodology because it would provide more detailed information. The selected risk analysis methodology was consistent with the risk evaluation criteria. Firstly, they used a list of potential incident scenarios to assess their potential impact. In addition, the likelihood of incident scenarios was defined and assessed. Finally, the level of risk was defined as low.
In the end, the level of risk was compared to the risk evaluation and acceptance criteria and was prioritized accordingly.
Based on the scenario above, answer the following question:
What type of risk identification approach did Printary use?
- A . Asset-based approach
- B . Event-based approach
- C . Threat-based approach
B
Explanation:
An event-based approach to risk identification focuses on identifying events that could negatively affect the achievement of the organization’s objectives. In the scenario, Printary used a list of identified events (e.g., errors in use and data corruption) that could negatively impact their information security objectives. This indicates that they considered specific events that might lead to information security incidents, which is characteristic of an event-based approach. Option B is correct because it aligns with the method described in the scenario. Option A (Asset-based approach) focuses on identifying risks based on assets, while Option C (Threat-based approach) focuses on threats rather than specific events, making them both incorrect in this context.
Scenario 3: Printary is an American company that offers digital printing services. Creating cost-effective and creative products, the company has been part of the printing industry for more than 30 years. Three years ago, the company started to operate online, providing greater flexibility for its clients. Through the website, clients could find information about all services offered by Printary and order personalized products. However, operating online increased the risk of cyber threats, consequently, impacting the business functions of the company. Thus, along with the decision of creating an online business, the company focused on managing information security risks. Their risk management program was established based on ISO/IEC 27005 guidelines and industry best practices.
Last year, the company considered the integration of an online payment system on its website in order to provide more flexibility and transparency to customers. Printary analyzed various available solutions and selected Pay0, a payment processing solution that allows any company to easily collect payments on their website. Before making the decision, Printary conducted a risk assessment to identify and analyze information security risks associated with the software. The risk assessment process involved three phases: identification, analysis, and evaluation. During risk identification, the company inspected assets, threats, and vulnerabilities. In addition, to identify the information security risks, Printary used a list of the identified events that could negatively affect the achievement of information security objectives. The risk identification phase highlighted two main threats associated with the online payment system: error in use and data corruption After conducting a gap analysis, the company concluded that the existing security controls were sufficient to mitigate the threat of data corruption. However, the user interface of the payment solution was complicated, which could increase the risk associated with user errors, and, as a result, impact data integrity and confidentiality.
Subsequently, the risk identification results were analyzed. The company conducted risk analysis in order to understand the nature of the identified risks. They decided to use a quantitative risk analysis methodology because it would provide more detailed information. The selected risk analysis methodology was consistent with the risk evaluation criteria. Firstly, they used a list of potential incident scenarios to assess their potential impact. In addition, the likelihood of incident scenarios was defined and assessed. Finally, the level of risk was defined as low.
In the end, the level of risk was compared to the risk evaluation and acceptance criteria and was prioritized accordingly.
Based on the scenario above, answer the following question:
What type of risk identification approach did Printary use?
- A . Asset-based approach
- B . Event-based approach
- C . Threat-based approach
B
Explanation:
An event-based approach to risk identification focuses on identifying events that could negatively affect the achievement of the organization’s objectives. In the scenario, Printary used a list of identified events (e.g., errors in use and data corruption) that could negatively impact their information security objectives. This indicates that they considered specific events that might lead to information security incidents, which is characteristic of an event-based approach. Option B is correct because it aligns with the method described in the scenario. Option A (Asset-based approach) focuses on identifying risks based on assets, while Option C (Threat-based approach) focuses on threats rather than specific events, making them both incorrect in this context.
Scenario 4: In 2017, seeing that millions of people turned to online shopping, Ed and James Cordon founded the online marketplace for footwear called Poshoe. In the past, purchasing pre-owned designer shoes online was not a pleasant experience because of unattractive pictures and an inability to ascertain the products’ authenticity. However, after Poshoe’s establishment, each product was well advertised and certified as authentic before being offered to clients. This increased the customers’ confidence and trust in Poshoe’s products and services. Poshoe has approximately four million users and its mission is to dominate the second-hand sneaker market and become a multi-billion dollar company.
Due to the significant increase of daily online buyers, Poshoe’s top management decided to adopt a big data analytics tool that could help the company effectively handle, store, and analyze data. Before initiating the implementation process, they decided to conduct a risk assessment. Initially, the company identified its assets, threats, and vulnerabilities associated with its information systems. In terms of assets, the company identified the information that was vital to the achievement of the organization’s mission and objectives. During this phase, the company also detected a rootkit in their software, through which an attacker could remotely access Poshoe’s systems and acquire sensitive data.
The company discovered that the rootkit had been installed by an attacker who had gained administrator access. As a result, the attacker was able to obtain the customers’ personal data after they purchased a product from Poshoe. Luckily, the company was able to execute some scans from the target device and gain greater visibility into their software’s settings in order to identify the vulnerability of the system.
The company initially used the qualitative risk analysis technique to assess the consequences and the likelihood and to determine the level of risk. The company defined the likelihood of risk as “a few times in two years with the probability of 1 to 3 times per year.” Later, it was decided that they would use a quantitative risk analysis methodology since it would provide additional information on this major risk. Lastly, the top management decided to treat the risk immediately as it could expose the company to other issues. In addition, it was communicated to their employees that they should update, secure, and back up Poshoe’s software in order to protect customers’ personal information and prevent unauthorized access from attackers.
According to scenario 4, Poshoe has identified its assets, vulnerabilities, and threats associated with its information systems .
What does the company need in order to start identifying its existing controls?
- A . The risk treatment implementation plan and documentation of controls
- B . A list of all existing and planned controls
- C . A list of incident scenarios with their consequences
B
Explanation:
To start identifying its existing controls, Poshoe needs a list of all existing and planned controls. This list will provide the necessary baseline to understand what security measures are already in place and what measures are planned to mitigate risks. This helps in determining gaps, evaluating the effectiveness of current controls, and identifying areas requiring improvement. Option A (The risk treatment implementation plan and documentation of controls) is incorrect because it is too specific and assumes a level of completion not indicated in the scenario. Option C (A list of incident scenarios with their consequences) is incorrect as it pertains to the analysis phase of risk management, not the identification of existing controls.
Scenario 2: Travivve is a travel agency that operates in more than 100 countries. Headquartered in San Francisco, the US, the agency is known for its personalized vacation packages and travel services. Travivve aims to deliver reliable services that meet its clients’ needs. Considering the impact of information security in its reputation, Travivve decided to implement an information security management system (ISMS) based on ISO/IEC 2700 1. In addition, they decided to establish and implement an information security risk management program. Based on the priority of specific departments in Travivve, the top management decided to initially apply the risk management process only in the Sales Management Department. The process would be applicable for other departments only when introducing new technology.
Travivve’s top management wanted to make sure that the risk management program is established based on the industry best practices. Therefore, they created a team of three members that would be responsible for establishing and implementing it. One of the team members was Travivve’s risk manager who was responsible for supervising the team and planning all risk management activities. In addition, the risk manager was responsible for monitoring the program and reporting the monitoring results to the top management.
Initially, the team decided to analyze the internal and external context of Travivve. As part of the process of understanding the organization and its context, the team identified key processes and activities. Then, the team identified the interested parties and their basic requirements and determined the status of compliance with these requirements. In addition, the team identified all the reference documents that applied to the defined scope of the risk management process, which mainly included the Annex A of ISO/IEC 27001 and the internal security rules established by Travivve. Lastly, the team analyzed both reference documents and justified a few noncompliances with those requirements.
The risk manager selected the information security risk management method which was aligned with other approaches used by the company to manage other risks. The team also communicated the risk management process to all interested parties through previously established communication mechanisms. In addition, they made sure to inform all interested parties about their roles and responsibilities regarding risk management. Travivve also decided to involve interested parties in its risk management activities since, according to the top management, this process required their active participation.
Lastly, Travivve’s risk management team decided to conduct the initial information security risk assessment process. As such, the team established the criteria for performing the information security risk assessment which included the consequence criteria and likelihood criteria.
Based on scenario 2, has Travivve defined the responsibilities of the risk manager appropriately?
- A . Yes, the risk manager should be responsible for all actions defined bv Traviwe
- B . No, the risk manager should not be responsible for planning all risk management activities
- C . No, the risk manager should not be responsible for reporting the monitoring results of the risk management program to the top management
A
Explanation:
ISO/IEC 27005 recommends that the risk manager or a designated authority should oversee the entire risk management process, including planning, monitoring, and reporting. In the scenario, the risk manager is responsible for supervising the team, planning all risk management activities, monitoring the program, and reporting the results to top management. This allocation of responsibilities is aligned with the guidelines of ISO/IEC 27005, which emphasizes that a risk manager should coordinate and manage all aspects of the risk management process to ensure its effectiveness and alignment with the organization’s objectives. Therefore, assigning these responsibilities to the risk manager is appropriate, making option A the correct answer.
Reference: ISO/IEC 27005:2018, Clause 5.3, "Roles and responsibilities," which specifies that those managing risk should have defined roles and should coordinate all activities in the risk management process.
Scenario 2: Travivve is a travel agency that operates in more than 100 countries. Headquartered in San Francisco, the US, the agency is known for its personalized vacation packages and travel services. Travivve aims to deliver reliable services that meet its clients’ needs. Considering the impact of information security in its reputation, Travivve decided to implement an information security management system (ISMS) based on ISO/IEC 2700 1. In addition, they decided to establish and implement an information security risk management program. Based on the priority of specific departments in Travivve, the top management decided to initially apply the risk management process only in the Sales Management Department. The process would be applicable for other departments only when introducing new technology.
Travivve’s top management wanted to make sure that the risk management program is established based on the industry best practices. Therefore, they created a team of three members that would be responsible for establishing and implementing it. One of the team members was Travivve’s risk manager who was responsible for supervising the team and planning all risk management activities. In addition, the risk manager was responsible for monitoring the program and reporting the monitoring results to the top management.
Initially, the team decided to analyze the internal and external context of Travivve. As part of the process of understanding the organization and its context, the team identified key processes and activities. Then, the team identified the interested parties and their basic requirements and determined the status of compliance with these requirements. In addition, the team identified all the reference documents that applied to the defined scope of the risk management process, which mainly included the Annex A of ISO/IEC 27001 and the internal security rules established by Travivve. Lastly, the team analyzed both reference documents and justified a few noncompliances with those requirements.
The risk manager selected the information security risk management method which was aligned with other approaches used by the company to manage other risks. The team also communicated the risk management process to all interested parties through previously established communication mechanisms. In addition, they made sure to inform all interested parties about their roles and responsibilities regarding risk management. Travivve also decided to involve interested parties in its risk management activities since, according to the top management, this process required their active participation.
Lastly, Travivve’s risk management team decided to conduct the initial information security risk assessment process. As such, the team established the criteria for performing the information security risk assessment which included the consequence criteria and likelihood criteria.
Based on scenario 2, has Travivve defined the responsibilities of the risk manager appropriately?
- A . Yes, the risk manager should be responsible for all actions defined bv Traviwe
- B . No, the risk manager should not be responsible for planning all risk management activities
- C . No, the risk manager should not be responsible for reporting the monitoring results of the risk management program to the top management
A
Explanation:
ISO/IEC 27005 recommends that the risk manager or a designated authority should oversee the entire risk management process, including planning, monitoring, and reporting. In the scenario, the risk manager is responsible for supervising the team, planning all risk management activities, monitoring the program, and reporting the results to top management. This allocation of responsibilities is aligned with the guidelines of ISO/IEC 27005, which emphasizes that a risk manager should coordinate and manage all aspects of the risk management process to ensure its effectiveness and alignment with the organization’s objectives. Therefore, assigning these responsibilities to the risk manager is appropriate, making option A the correct answer.
Reference: ISO/IEC 27005:2018, Clause 5.3, "Roles and responsibilities," which specifies that those managing risk should have defined roles and should coordinate all activities in the risk management process.
An internal employee clicks on a link embedded in an email that redirects them to an unsecured website, installing a malware on the device.
The likelihood of occurrence for the first risk scenario was determined as “medium.” One of the main reasons that such a risk could occur was the usage of default accounts and password. Attackers could exploit this vulnerability and launch a brute-force attack. Therefore, Productscape decided to start using an automated “build and deploy” process which would test the software on deploy and minimize the likelihood of such an incident from happening. However, the team made it clear that the implementation of this process would not eliminate the risk completely and that there was still a low possibility for this risk to occur. Productscape documented the remaining risk and decided to monitor it for changes.
The likelihood of occurrence for the second risk scenario was determined as “medium.” Productscape decided to contract an IT company that would provide technical assistance and monitor the company’s systems and networks in order to prevent such incidents from happening. The likelihood of occurrence for the third risk scenario was determined as “high.” Thus, Productscape decided to include phishing as a topic on their information security training sessions. In addition, Alex reviewed the controls of Annex A of ISO/IEC 27001 in order to determine the necessary controls for treating this risk. Alex decided to implement control A.8.23 Web filtering which would help the company to reduce the risk of accessing unsecure websites. Although security controls were implemented to treat the risk, the level of the residual risk still did not meet the risk acceptance criteria defined in the beginning of the risk assessment process. Since the cost of implementing additional controls was too high for the company, Productscape decided to accept the residual risk. Therefore, risk owners were assigned the responsibility of managing the residual risk.
Based on scenario 6, Productscape decided to monitor the remaining risk after risk treatment. Is this necessary?
- A . No, there is no need to monitor risks that meet the risk acceptance criteria
- B . No, unless the risk has a severe impact if it occurs, there is no need to monitor the risk
- C . Yes, the remaining risk after risk treatment should be monitored and reviewed
C
Explanation:
ISO/IEC 27005 advises that even after risks have been treated, any residual risks should be continuously monitored and reviewed. This is necessary to ensure that they remain within acceptable levels and that any changes in the internal or external environment do not escalate the risk beyond acceptable thresholds. Monitoring also ensures that the effectiveness of the controls remains adequate over time. Option A is incorrect because all risks, including those meeting the risk acceptance criteria, should be monitored. Option B is incorrect because monitoring is necessary regardless of the perceived severity if it occurs, to detect changes early.
An internal employee clicks on a link embedded in an email that redirects them to an unsecured website, installing a malware on the device.
The likelihood of occurrence for the first risk scenario was determined as “medium.” One of the main reasons that such a risk could occur was the usage of default accounts and password. Attackers could exploit this vulnerability and launch a brute-force attack. Therefore, Productscape decided to start using an automated “build and deploy” process which would test the software on deploy and minimize the likelihood of such an incident from happening. However, the team made it clear that the implementation of this process would not eliminate the risk completely and that there was still a low possibility for this risk to occur. Productscape documented the remaining risk and decided to monitor it for changes.
The likelihood of occurrence for the second risk scenario was determined as “medium.” Productscape decided to contract an IT company that would provide technical assistance and monitor the company’s systems and networks in order to prevent such incidents from happening. The likelihood of occurrence for the third risk scenario was determined as “high.” Thus, Productscape decided to include phishing as a topic on their information security training sessions. In addition, Alex reviewed the controls of Annex A of ISO/IEC 27001 in order to determine the necessary controls for treating this risk. Alex decided to implement control A.8.23 Web filtering which would help the company to reduce the risk of accessing unsecure websites. Although security controls were implemented to treat the risk, the level of the residual risk still did not meet the risk acceptance criteria defined in the beginning of the risk assessment process. Since the cost of implementing additional controls was too high for the company, Productscape decided to accept the residual risk. Therefore, risk owners were assigned the responsibility of managing the residual risk.
Based on scenario 6, Productscape decided to monitor the remaining risk after risk treatment. Is this necessary?
- A . No, there is no need to monitor risks that meet the risk acceptance criteria
- B . No, unless the risk has a severe impact if it occurs, there is no need to monitor the risk
- C . Yes, the remaining risk after risk treatment should be monitored and reviewed
C
Explanation:
ISO/IEC 27005 advises that even after risks have been treated, any residual risks should be continuously monitored and reviewed. This is necessary to ensure that they remain within acceptable levels and that any changes in the internal or external environment do not escalate the risk beyond acceptable thresholds. Monitoring also ensures that the effectiveness of the controls remains adequate over time. Option A is incorrect because all risks, including those meeting the risk acceptance criteria, should be monitored. Option B is incorrect because monitoring is necessary regardless of the perceived severity if it occurs, to detect changes early.
Scenario 7: Adstry is a business growth agency that specializes in digital marketing strategies. Adstry helps organizations redefine the relationships with their customers through innovative solutions. Adstry is headquartered in San Francisco and recently opened two new offices in New York. The structure of the company is organized into teams which are led by project managers. The project manager has the full power in any decision related to projects. The team members, on the other hand, report the project’s progress to project managers.
Considering that data breaches and ad fraud are common threats in the current business environment, managing risks is essential for Adstry. When planning new projects, each project manager is responsible for ensuring that risks related to a particular project have been identified, assessed, and mitigated. This means that project managers have also the role of the risk manager in Adstry. Taking into account that Adstry heavily relies on technology to complete their projects, their risk assessment certainly involves identification of risks associated with the use of information technology. At the earliest stages of each project, the project manager communicates the risk assessment results to its team members.
Adstry uses a risk management software which helps the project team to detect new potential risks during each phase of the project. This way, team members are informed in a timely manner for the new potential risks and are able to respond to them accordingly. The project managers are responsible for ensuring that the information provided to the team members is communicated using an appropriate language so it can be understood by all of them.
In addition, the project manager may include external interested parties affected by the project in the risk communication. If the project manager decides to include interested parties, the risk communication is thoroughly prepared. The project manager firstly identifies the interested parties that should be informed and takes into account their concerns and possible conflicts that may arise due to risk communication. The risks are communicated to the identified interested parties while taking into consideration the confidentiality of Adstry’s information and determining the level of detail that should be included in the risk communication. The project managers use the same risk management software for risk communication with external interested parties since it provides a consistent view of risks. For each project, the project manager arranges regular meetings with relevant interested parties of the project, they discuss the detected risks, their prioritization, and determine appropriate treatment solutions. The information taken from the risk management software and the results of these meetings are documented and are used for decision-making processes. In addition, the company uses a computerized documented information management system for the acquisition, classification, storage, and archiving of its documents.
Based on scenario 7, the risk management software is used to help Adstry’s teams to detect new risks throughout all phases of the project. Is this necessary?
- A . Yes, Adstry; should establish adequate procedures to monitor and review risks on a regular basis in order to identity the changes at an early stage
- B . Yes, according to ISO/IEC 27005, Adstry; must use an automated solution for identifying and analyzing risks related to information technology throughout all phases of a project
- C . No. monitoring risks after a project is initiated will not provide important information that could impact Adstry’.s business objectives
A
Explanation:
According to ISO/IEC 27005, it is essential to establish procedures for the continuous monitoring and review of risks to identify changes in the risk environment at an early stage. This ongoing monitoring process helps ensure that new risks are detected promptly and that existing controls remain effective. Option B is incorrect because while automation can aid in risk management, ISO/IEC 27005 does not mandate the use of automated solutions specifically. Option C is incorrect because monitoring risks after a project is initiated is crucial for adapting to changing conditions and protecting business objectives.
Activity area 4: The organization identifies and evaluates the risks. In addition, the criteria specified in activity area 1 is reviewed and the consequences of the areas of concerns are evaluated. Lastly, the level of identified risks is determined.
The table below provides an example of how Biotide assesses the risks related to its information assets following this methodology:
Based on the table provided in scenario 8, did Biotide prioritize the security requirements for electronic health records?
- A . Yes, Biotide determined confidentiality as the most important security requirement for electronic health records
- B . Yes, Biotide prioritized the security requirements for electronic health records when prioritizing
the areas of concern - C . No, Biotide did not prioritize security requirements for electronic health records
A
Explanation:
Based on the table provided in Scenario 8, Biotide has prioritized the security requirements for its electronic health records. In Activity Area 2, the table clearly indicates that confidentiality is considered the most important security feature for electronic health records. This prioritization is based on the need to ensure that only authorized users have access to these critical information assets due to the sensitive nature of the data involved.
The emphasis on confidentiality aligns with ISO/IEC 27005 guidelines, which recommend prioritizing security requirements based on the impact assessment and the organization’s risk management objectives. In this case, the potential impact of unauthorized access (breach of confidentiality) to electronic health records is high, which justifies Biotide’s decision to prioritize confidentiality over other security requirements such as integrity or availability.
Option A is correct because it reflects the prioritization decision documented in the table, while options B and C are inaccurate as they either misrepresent the prioritization process or suggest that it did not occur.
Activity area 4: The organization identifies and evaluates the risks. In addition, the criteria specified in activity area 1 is reviewed and the consequences of the areas of concerns are evaluated. Lastly, the level of identified risks is determined.
The table below provides an example of how Biotide assesses the risks related to its information assets following this methodology:
Based on the table provided in scenario 8, did Biotide prioritize the security requirements for electronic health records?
- A . Yes, Biotide determined confidentiality as the most important security requirement for electronic health records
- B . Yes, Biotide prioritized the security requirements for electronic health records when prioritizing
the areas of concern - C . No, Biotide did not prioritize security requirements for electronic health records
A
Explanation:
Based on the table provided in Scenario 8, Biotide has prioritized the security requirements for its electronic health records. In Activity Area 2, the table clearly indicates that confidentiality is considered the most important security feature for electronic health records. This prioritization is based on the need to ensure that only authorized users have access to these critical information assets due to the sensitive nature of the data involved.
The emphasis on confidentiality aligns with ISO/IEC 27005 guidelines, which recommend prioritizing security requirements based on the impact assessment and the organization’s risk management objectives. In this case, the potential impact of unauthorized access (breach of confidentiality) to electronic health records is high, which justifies Biotide’s decision to prioritize confidentiality over other security requirements such as integrity or availability.
Option A is correct because it reflects the prioritization decision documented in the table, while options B and C are inaccurate as they either misrepresent the prioritization process or suggest that it did not occur.