New Year Sale ! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

PECB Exam ISO-IEC-27005-Risk-Manager Topic 3 Question 14 Discussion

Actual exam question for PECB's ISO-IEC-27005-Risk-Manager exam
Question #: 14
Topic #: 3
[All ISO-IEC-27005-Risk-Manager Questions]

Scenario 6: Productscape is a market research company headquartered in Brussels, Belgium. It helps organizations understand the needs and expectations of their customers and identify new business opportunities. Productscape's teams have extensive experience in marketing and business strategy and work with some of the best-known organizations in Europe. The industry in which Productscape operates requires effective risk management. Considering that Productscape has access to clients' confidential information, it is responsible for ensuring its security. As such, the company conducts regular risk assessments. The top management appointed Alex as the risk manager, who is responsible for monitoring the risk management process and treating information security risks.

The last risk assessment conducted was focused on information assets. The purpose of this risk assessment was to identify information security risks, understand their level, and take appropriate action to treat them in order to ensure the security of their systems. Alex established a team of three members to perform the risk assessment activities. Each team member was responsible for specific departments included in the risk assessment scope. The risk assessment provided valuable information to identify, understand, and mitigate the risks that Productscape faces.

Initially, the team identified potential risks based on the risk identification results. Prior to analyzing the identified risks, the risk acceptance criteria were established. The criteria for accepting the risks were determined based on Productscape's objectives, operations, and technology. The team created various risk scenarios and determined the likelihood of occurrence as ''low,'' ''medium,'' or ''high.'' They decided that if the likelihood of occurrence for a risk scenario is determined as ''low,'' no further action would be taken. On the other hand, if the likelihood of occurrence for a risk scenario is determined as ''high'' or ''medium,'' additional controls will be implemented. Some information security risk scenarios defined by Productscape's team were as follows:

1. A cyber attacker exploits a security misconfiguration vulnerability of Productscape's website to launch an attack, which, in turn, could make the website unavailable to users.

2. A cyber attacker gains access to confidential information of clients and may threaten to make the information publicly available unless a ransom is paid.

3. 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?

Show Suggested Answer Hide Answer
Suggested Answer: C

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.


Contribute your Thoughts:

Heike
1 days ago
I wouldn't say monitoring is *always* necessary, but in this scenario where the risk is still unacceptably high, it's the responsible thing to do. Gotta keep an eye on those security vulnerabilities.
upvoted 0 times
...
Veronika
2 days ago
I agree, monitoring is crucial. Productscape is dealing with sensitive client data, they can't afford to let their guard down. That residual risk needs to be on their radar at all times.
upvoted 0 times
...
Claribel
6 days ago
I agree, it's important to ensure that the risk is still under control.
upvoted 0 times
...
Willow
7 days ago
I think the remaining risk should be monitored and reviewed.
upvoted 0 times
...
Jaime
7 days ago
Definitely need to monitor the remaining risk. You can't just set it and forget it, especially with information security. Who knows when the threat landscape could change and that 'low' risk becomes a serious problem.
upvoted 0 times
Nu
1 days ago
A) No, there is no need to monitor risks that meet the risk acceptance criteria
upvoted 0 times
...
...

Save Cancel