According to ISO/IEC 27000, what is the definition of information security?
Answer : A
According to ISO/IEC 27000, information security is defined as the 'preservation of confidentiality, integrity, and availability of information.' This definition highlights the three core principles of information security:
Confidentiality ensures that information is not disclosed to unauthorized individuals or systems.
Integrity ensures the accuracy and completeness of information and its processing methods.
Availability ensures that authorized users have access to information and associated assets when required.
This definition encompasses the protection of information in all forms and aligns with ISO/IEC 27005's guidelines on managing information security risks. Therefore, option A is the correct answer. Options B and C are incorrect as they refer to more specific aspects or other areas of information management.
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.
Based on the scenario above, answer the following question:
Travivve decided to initially apply the risk management process only in the Sales Management Department. Is this acceptable?
Answer : B
ISO/IEC 27005 provides guidance on risk management for information security, and it allows flexibility in applying the risk management process to different parts of an organization. The decision to initially apply the risk management process only to the Sales Management Department is acceptable under ISO/IEC 27005, as the standard supports the selective application of risk management activities based on the specific needs and priorities of the organization. This is in line with risk management best practices, where organizations may focus on critical areas first (such as high-risk departments or those that handle sensitive information) and later expand the process as needed. Therefore, applying the risk management process to a subset of departments is appropriate, making option B the correct answer.
ISO/IEC 27005:2018, Clause 7, 'Context Establishment,' which allows defining the scope and boundaries of risk management as relevant to the organization's needs.
ISO/IEC 27001:2013, Clause 4.3, 'Determining the scope of the information security management system,' which also permits defining a scope based on priorities and relevance.
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 accept the residual risk and risk owners were assigned the responsibility of managing this risk.
Based on the guidelines of ISO/IEC 27005, is this acceptable?
Answer : A
ISO/IEC 27005 specifies that once a risk treatment has been applied and residual risk remains, it is essential that the risk owner is aware of this residual risk and accepts the responsibility for managing it. The risk owner is the individual or entity accountable for managing specific risks within the organization. In Scenario 6, Productscape decided to accept the residual risk and assigned risk owners the responsibility for managing it, which is fully compliant with ISO/IEC 27005. Thus, the correct answer is A.
ISO/IEC 27005:2018, Clause 8.6, 'Risk Treatment,' which states that risk owners should be aware of and accept responsibility for managing residual risks.
Scenario 8: Biotide is a pharmaceutical company that produces medication for treating different kinds of diseases. The company was founded in 1997, and since then it has contributed in solving some of the most challenging healthcare issues.
As a pharmaceutical company, Biotide operates in an environment associated with complex risks. As such, the company focuses on risk management strategies that ensure the effective management of risks to develop high-quality medication. With the large amount of sensitive information generated from the company, managing information security risks is certainly an important part of the overall risk management process. Biotide utilizes a publicly available methodology for conducting risk assessment related to information assets. This methodology helps Biotide to perform risk assessment by taking into account its objectives and mission. Following this method, the risk management process is organized into four activity areas, each of them involving a set of activities, as provided below.
1. Activity area 1: The organization determines the criteria against which the effects of a risk occurring can be evaluated. In addition, the impacts of risks are also defined.
2. Activity area 2: The purpose of the second activity area is to create information asset profiles. The organization identifies critical information assets, their owners, as well as the security requirements for those assets. After determining the security requirements, the organization prioritizes them. In addition, the organization identifies the systems that store, transmit, or process information.
3. Activity area 3: The organization identifies the areas of concern which initiates the risk identification process. In addition, the organization analyzes and determines the probability of the occurrence of possible threat scenarios.
4. 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 scenario above, answer the following question:

Which risk assessment methodology does Biotide use?
Answer : A
Biotide uses the OCTAVE Allegro methodology for risk assessment. This is determined based on the description of the activities mentioned in the scenario. OCTAVE Allegro is a streamlined approach specifically designed to help organizations perform risk assessments that are efficient and effective, particularly when handling information assets. The methodology focuses on a thorough examination of information assets, the threats they face, and the impact of those threats.
Activity Area 1: OCTAVE Allegro defines the criteria for evaluating the impact of risks, which is consistent with determining the risk effects' evaluation criteria in the scenario.
Activity Area 2: In OCTAVE Allegro, a critical step is creating profiles for information assets, identifying their owners, and determining security requirements. This aligns with the activity in which Biotide identifies critical assets, their owners, and their security needs.
Activity Area 3: Identifying areas of concern that initiate risk identification and analyzing threat scenarios is central to OCTAVE Allegro. This is reflected in the activity of identifying areas of concern and determining the likelihood of threats.
Activity Area 4: Evaluating the risks, reviewing criteria, and determining risk levels corresponds to the latter stages of OCTAVE Allegro, where risks are prioritized based on the likelihood and impact, and risk management strategies are formulated accordingly.
The steps outlined align with the OCTAVE Allegro approach, which focuses on understanding and addressing information security risks comprehensively and in line with organizational objectives. Hence, option A, OCTAVE Allegro, is the correct answer.
ISO/IEC 27005:2018 emphasizes the importance of using structured methodologies for information security risk management, like OCTAVE Allegro, to ensure that risks are consistently identified, assessed, and managed in accordance with organizational risk tolerance and objectives.
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?
Answer : B
Poshoe used scans from the target device to gain greater visibility into their software's settings and identify vulnerabilities, which indicates the use of a host-based scanning tool. Host-based scanning tools are used to examine the internal state of a system, such as installed software, configurations, and files, to detect vulnerabilities or malicious software like rootkits. Option A (Network-based scanning tool) would be used to scan network traffic and identify vulnerabilities in network devices, which does not match the context. Option C (Penetration testing tool) involves simulating an attack to test system defenses, which is more intrusive than the scanning described in the scenario.
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 criteri
a. 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 scenario 3, what does the complicated user interface of the software which could lead to error present?
Answer : A
ISO/IEC 27005 defines a vulnerability as a weakness in an asset or control that could potentially be exploited by one or more threats. In the scenario, the complicated user interface of the payment software represents a weakness that could lead to user errors, potentially impacting data integrity and confidentiality. This aligns with the definition of a vulnerability, as it is a weakness that could be exploited by threats (e.g., errors in use). Therefore, the complicated user interface is correctly identified as a vulnerability, making option A the correct answer.
ISO/IEC 27005:2018, Clause 8.3, 'Risk Identification,' where vulnerabilities are identified as weaknesses that can be exploited by threats.
Scenario 5: Detika is a private cardiology clinic in Pennsylvania, the US. Detika has one of the most advanced healthcare systems for treating heart diseases. The clinic uses sophisticated apparatus that detects heart diseases in early stages. Since 2010, medical information of Detika's patients is stored on the organization's digital systems. Electronic health records (EHR), among others, include patients' diagnosis, treatment plan, and laboratory results.
Storing and accessing patient and other medical data digitally was a huge and a risky step for Detik
a. Considering the sensitivity of information stored in their systems, Detika conducts regular risk assessments to ensure that all information security risks are identified and managed. Last month, Detika conducted a risk assessment which was focused on the EHR system. During risk identification, the IT team found out that some employees were not updating the operating systems regularly. This could cause major problems such as a data breach or loss of software compatibility. In addition, the IT team tested the software and detected a flaw in one of the software modules used. Both issues were reported to the top management and they decided to implement appropriate controls for treating the identified risks. They decided to organize training sessions for all employees in order to make them aware of the importance of the system updates. In addition, the manager of the IT Department was appointed as the person responsible for ensuring that the software is regularly tested.
Another risk identified during the risk assessment was the risk of a potential ransomware attack. This risk was defined as low because all their data was backed up daily. The IT team decided to accept the actual risk of ransomware attacks and concluded that additional measures were not required. This decision was documented in the risk treatment plan and communicated to the risk owner. The risk owner approved the risk treatment plan and documented the risk assessment results.
Following that, Detika initiated the implementation of new controls. In addition, one of the employees of the IT Department was assigned the responsibility for monitoring the implementation process and ensure the effectiveness of the security controls. The IT team, on the other hand, was responsible for allocating the resources needed to effectively implement the new controls.
Based on scenario 5, which risk treatment option did Detika select to treat the risk of a potential ransomware attack?
Answer : A
Risk retention involves accepting the risk when its likelihood or impact is low, or when the cost of mitigating the risk is higher than the benefit. In the scenario, Detika decided to accept the risk of a potential ransomware attack because the data is backed up daily, and additional measures were deemed unnecessary. This decision aligns with the risk retention strategy, where an organization chooses to live with the risk rather than apply further controls. Option A is the correct answer.
ISO/IEC 27005:2018, Clause 8.6, 'Risk Treatment,' which discusses risk retention as an option for managing risks deemed acceptable by the organization.