PECB ISO-IEC-27005-Risk-Manager

Not sure whether Dumpkiller is right for you? Download the free ISO-IEC-27005-Risk-Manager demo and review a sample of our 62 PECB Certified ISO/IEC 27005 Risk Manager practice questions before you spend a cent.

PECB ISO-IEC-27005-Risk-Manager Exam Overview:

PECB ISO-IEC-27005-Risk-Manager Exam Syllabus Topics:

Your ISO-IEC-27005-Risk-Manager Exam Questions, Answered

What is the ISO-IEC-27005-Risk-Manager exam all about?

The PECB Certified ISO/IEC 27005 Risk Manager exam (code: ISO-IEC-27005-Risk-Manager) is the official PECB exam that leads to the PECB Certified ISO/IEC 27005 Risk Manager certification. It sits at the Manager level of the PECB certification track. It is also connected with related credentials such as PECB Certified ISO/IEC 27005 Provisional Risk Manager, PECB Certified ISO/IEC 27005 Lead Risk Manager. Passing it proves to employers that your skills have been validated by PECB itself, which is why the ISO-IEC-27005-Risk-Manager credential keeps showing up in job postings.

How many questions are in the ISO-IEC-27005-Risk-Manager exam, and how long does it take?

The PECB Certified ISO/IEC 27005 Risk Manager exam gives you 120 minutes to work through 60. Pacing matters more than most candidates expect, so before exam day, run at least one full timed session in the Dumpkiller test engine to learn how long you can afford per question. If an item stalls you, flag it and move on — coming back later beats burning five minutes on a single question.

What score do I need to pass the ISO-IEC-27005-Risk-Manager exam, and how much does it cost?

The passing score for the PECB Certified ISO/IEC 27005 Risk Manager exam is 70%, and the official registration fee is $300 - $450 USD. Remember that a failed attempt means paying that fee in full again, so a timed self-assessment with Dumpkiller practice questions about a week before your exam date is a cheap way to confirm you are scoring comfortably above 70%.

Are there any prerequisites for the ISO-IEC-27005-Risk-Manager exam?

According to PECB, the following applies: Basic knowledge of information security and ISO/IEC 27001; no mandatory prior certification required; for full certification: 2 years professional experience including 1 year in risk management, 200 hours of relevant activities, sign PECB Code of Ethics. Certification policies do change from time to time, so confirm the latest requirements on the official exam page at https://pecb.com/en/education-and-certification-for-individuals/iso-iec-27005/iso-iec-27005-risk-manager before you register.

How do I register for the ISO-IEC-27005-Risk-Manager exam?

You can book your PECB Certified ISO/IEC 27005 Risk Manager exam through the official channels below:

• PECB Official Registration

Depending on availability in your region, the exam is delivered as Online proctored or onsite at authorized exam centers.

What official training does PECB recommend for the ISO-IEC-27005-Risk-Manager exam?

PECB lists the following training options for PECB Certified ISO/IEC 27005 Risk Manager candidates:

• PECB ISO/IEC 27005 Risk Manager Training Course

Official courses build a solid foundation, and pairing them with the 62 practice questions from Dumpkiller shows you how ready you really are before you spend money on the exam itself.

Can I try the ISO-IEC-27005-Risk-Manager practice questions before buying?

Yes. Dumpkiller offers a free ISO-IEC-27005-Risk-Manager PDF demo so you can review the question style, difficulty, and explanations before committing to anything. After purchase, your PECB Certified ISO/IEC 27005 Risk Manager material includes 365 days of free updates, and if your product expires after that, you can extend the update service at a 50% discount from your member zone.

What happens if I do not pass the ISO-IEC-27005-Risk-Manager exam, and how is my order delivered?

If you take the corresponding ISO-IEC-27005-Risk-Manager exam within 60 days of your purchase and do not pass, you can apply for a full refund under our 100% Money Back Guarantee, subject to a few conditions: the failed exam must be the one matching your purchase; sitting the exam within 3 days of purchase does not qualify, since that leaves too little preparation time; downloading the material without actually taking the exam does not qualify; free materials and expired orders are excluded; and the candidate name must match the payer name. To apply, send a scanned copy of your enrollment slip together with your official Score Report (PDF) within 2 days after the exam, and claims are processed within 7 days. If you would rather not take a refund, you can exchange your purchase for two free products of equal value while keeping the update service on the product you originally bought. As for delivery, everything is an instant download: your products are sent to your email within one minute of payment — contact customer service if nothing arrives within 2 hours — and there is no limit on the number of computers you can install the software on.

What topics are covered in the ISO-IEC-27005-Risk-Manager exam?

The official PECB Certified ISO/IEC 27005 Risk Manager syllabus is organized into 4 main domains. The first three are Fundamental Principles and Concepts of Information Security Risk Management (25%), Other Information Security Risk Assessment Methodologies (20%), and Information Security Risk Management Framework and Processes (30%). For the full domain-by-domain breakdown, see the complete Exam Topics outline above.

PECB Certified ISO/IEC 27005 Risk Manager Sample Questions:

Question #1

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.
Which risk treatment option was used for the second risk scenario? Refer to scenario 6.

A. Risk sharing
B. Risk avoidance
C. Risk retention

Question #2

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?

A. No, unless the risk has a severe impact if it occurs, there is no need to monitor the risk
B. Yes, the remaining risk after risk treatment should be monitored and reviewed
C. No, there is no need to monitor risks that meet the risk acceptance criteria

Question #3

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 27001. 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.
Did the risk management team establish all the criteria required to perform the information security risk assessment? Refer to scenario 2.

A. Yes. the risk management team established all the criteria that are necessary to perform an information security risk assessment
B. No, the risk management team should also establish the criteria for treating the identified risks
C. No, the risk management team should also establish the criteria for determining the level of risk

Question #4

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 dat a. 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.
Based on scenario 4, which scanning tool did Poshoe use to detect the vulnerability in their software?

A. Penetration testing tool
B. Network-based scanning tool
C. Host-based scanning tool

Question #5

Which of the following risk assessment methods provides an information security risk assessment methodology and involves three phases build asset-based threat profiles, identify infrastructure vulnerabilities, and develop security strategy and plans?

A. OCTAVE-S
B. MEHARI
C. TRA

Solutions: