ISO-IEC-27002-Foundation Exam Dumps - PECB ISO 27002 Questions and Answers

A digital customer identity is the best example of an organizational asset in cyberspace because it exists, functions, and is protected within digital systems, networks, applications, and online services. ISO/IEC 27002 treats identities, authentication information, access rights, and digital accounts as critical security subjects because compromise of identity can enable unauthorized access, fraud, impersonation, privacy breaches, and loss of accountability. A digital customer identity can include usernames, identifiers, credentials, account attributes, authentication factors, access permissions, profile data, and linked personal information. Medical data and intellectual property are also important information assets, but the phrase “asset in cyberspace” points most directly to a digitally represented identity used for electronic interaction. ISO/IEC 27002 contains several controls that protect this asset type, including identity management, authentication information, access rights, secure authentication, and access restriction. These controls ensure that identities are created, maintained, verified, modified, disabled, and removed in a controlled manner. The exam logic therefore favors option B because cyberspace emphasizes digital identity and online representation. References/Chapters: ISO/IEC 27002:2022, Control 5.16 Identity management; Control 5.17 Authentication information; Control 5.18 Access rights; Control 8.5 Secure authentication.

==========

Organizations can manage the security of large networks by dividing them into separate network domains and separating them from the public network where appropriate. This reflects the principle of network segregation, which reduces the ability of an attacker, malware, or unauthorized user to move freely across the environment. Separate domains can be based on trust level, business function, system criticality, data sensitivity, user group, supplier access, development environment, or regulatory requirement. ISO/IEC 27002 supports this through network security, network segregation, access control, and secure architecture practices. Option B is incorrect because including internal domains into the public network would increase exposure and weaken boundaries. Option C is not realistic or aligned with modern enterprise architecture; organizations often need integrated services, users, and systems, but they must integrate them securely. Segmentation allows controlled communication through firewalls, gateways, routing rules, access controls, monitoring, and filtering. The goal is not isolation for its own sake, but risk-based separation and controlled connectivity. Therefore, option A is verified. References/Chapters: ISO/IEC 27002:2022, Control 8.20 Network security; Control 8.22 Segregation of networks; Control 5.15 Access control.

==========

The purpose of Control 8.20, Network security, is to protect information in networks and supporting information processing facilities from compromise through the network. This includes protecting data in transit, network devices, network services, communication paths, routing, management interfaces, and connected systems. Network compromise can lead to unauthorized access, interception, malware propagation, denial of service, lateral movement, data exfiltration, or manipulation of traffic. Option B relates more closely to Control 8.21, Security of network services, which addresses security mechanisms, service levels, and management requirements for network services. Option C relates to Control 8.22, Segregation of networks, which specifically concerns splitting networks into security boundaries or domains. Control 8.20 is broader: it establishes the general objective of securing networks against compromise. ISO/IEC 27002 expects organizations to manage and control networks according to risk, including architecture, monitoring, authentication, encryption where needed, device hardening, and protection of network management functions. The correct answer is therefore option A. References/Chapters: ISO/IEC 27002:2022, Control 8.20 Network security; Control 8.21 Security of network services; Control 8.22 Segregation of networks.

==========

When establishing a remote working policy, organizations should consider the threat of unauthorized access to information or resources from other persons in public places. Remote working changes the security environment because employees may work from homes, hotels, airports, cafés, shared offices, client sites, or while travelling. These environments can expose information to shoulder surfing, overheard conversations, device theft, insecure Wi-Fi, unattended screens, family or visitor access, and uncontrolled printing or storage. ISO/IEC 27002 Control 6.7, Remote working, expects organizations to define security measures for remote work based on risk. This can include secure authentication, encryption, screen privacy, endpoint protection, physical protection of devices, secure network access, acceptable use, incident reporting, backup, and restrictions on handling sensitive information. Option B relates more to equipment siting and physical protection of facilities. Option C relates to access rights and privileged access management. Both can be relevant elsewhere, but the remote working policy question directly points to risks from other persons in public or uncontrolled locations. Therefore, option A is verified. References/Chapters: ISO/IEC 27002:2022, Control 6.7 Remote working; Control 7.9 Security of assets off-premises; Control 5.15 Access control.

Company A has implemented Control 8.23, Web filtering. Web filtering is intended to protect systems from compromise by preventing access to known malicious or inappropriate web resources. Blocking IP addresses or domains associated with malicious websites is a typical web filtering technique. It can reduce exposure to malware, phishing pages, command-and-control infrastructure, drive-by downloads, credential harvesting, and unauthorized content. Control 8.11, Data masking, is unrelated because it protects sensitive data by obscuring or substituting values so users or systems do not see the original data. Control 5.18, Access rights, concerns granting, reviewing, modifying, and removing user access privileges to information and systems. Browser configuration that blocks malicious destinations is not primarily user access rights management; it is filtering web traffic based on destination risk. ISO/IEC 27002 places web filtering under technological controls because it is implemented through browsers, gateways, DNS filtering, proxies, endpoint tools, or secure web gateways. Therefore, option B is verified. References/Chapters: ISO/IEC 27002:2022, Control 8.23 Web filtering; Control 8.7 Protection against malware; Control 8.20 Network security.

==========

The situation describes a people-related operational threat: data input error by employees. The root cause is not a malicious external attack or theft; it is that employees cannot reliably follow complicated processing procedures. ISO/IEC 27002 recognizes that people, competence, awareness, and documented procedures are essential to information security. When procedures are unclear, excessive, or difficult to follow, employees may enter incorrect data, omit fields, select wrong categories, mishandle classifications, misroute information, or unintentionally corrupt records. This primarily threatens integrity because the information may no longer be accurate or complete. Hacking would involve unauthorized technical intrusion, and information theft would involve intentional unauthorized taking or disclosure of information. Neither is stated in the scenario. ISO/IEC 27002 addresses this type of risk through information security awareness, education and training, documented operating procedures, clear responsibilities, and appropriate segregation of duties. Effective controls should make correct behavior practical and repeatable, not merely documented. Therefore, the verified answer is option A. References/Chapters: ISO/IEC 27002:2022, Control 6.3 Information security awareness, education and training; Control 5.37 Documented operating procedures; Control 5.3 Segregation of duties.

==========

Control 8.19, Installation of software on operational systems, aims to ensure the integrity of operational systems and prevent exploitation of technical vulnerabilities. Software installed in production can introduce malware, insecure configurations, untested functionality, compatibility problems, unauthorized tools, or vulnerable components. ISO/IEC 27002 therefore expects installation on operational systems to be controlled, authorized, tested, and managed. This protects live systems from unauthorized or inappropriate software that could weaken security or disrupt operations. Control 8.15, Logging, records events and supports monitoring, investigation, accountability, and detection, but it does not primarily control software installation. Control 8.17, Clock synchronization, ensures consistent time settings across systems so logs, events, and transactions can be correlated accurately. It is important but not the control aimed at preventing exploitation through software installation weaknesses. The exam phrase “integrity of operational systems” is directly aligned with controlling what software is installed in production. Therefore, option A is verified. References/Chapters: ISO/IEC 27002:2022, Control 8.19 Installation of software on operational systems; Control 8.8 Management of technical vulnerabilities; Control 8.32 Change management.

==========

Control 8.28, Secure coding, is the correct control because the question focuses on software being written securely and reducing potential vulnerabilities in the code. Secure coding addresses the practices, rules, and techniques developers should use to avoid common software weaknesses. This can include input validation, output encoding, error handling, authentication handling, secure session management, memory safety, protection against injection, secure API use, cryptographic correctness, dependency management, and code review. Control 8.29, Security testing in development and acceptance, verifies whether security requirements and controls are effective, but testing occurs after or during development and does not itself define how code should be written. Control 8.26, Application security requirements, defines security requirements for applications, but secure coding is the specific implementation practice that reduces vulnerabilities during software construction. ISO/IEC 27002 treats secure development as a lifecycle discipline: requirements define what is needed, secure coding implements it safely, and testing validates it. The direct match to the exam wording is Control 8.28. References/Chapters: ISO/IEC 27002:2022, Control 8.28 Secure coding; Control 8.26 Application security requirements; Control 8.29 Security testing in development and acceptance.

==========

Access control software that allows only authorized employees to access sensitive files is a preventive control. Its purpose is to stop unauthorized access before it occurs by enforcing approved access rules. In ISO/IEC 27002, access control is implemented through policies, identity management, authentication, authorization, access rights review, privileged access control, and restrictions on information access. This type of software can prevent unauthorized disclosure, unauthorized modification, misuse of sensitive data, and violation of privacy or contractual obligations. It is not primarily detective because it does not merely discover an event after it has happened. It is not corrective because it does not restore damaged information or reverse the impact of an incident. Its security value is in blocking access attempts that do not meet authorization criteria. The principle behind the control is least privilege: users should receive only the access necessary for their role and responsibilities. For sensitive files, this is especially important because confidentiality, integrity, and accountability depend on correct authorization. References/Chapters: ISO/IEC 27002:2022, Control 5.15 Access control; Control 5.16 Identity management; Control 5.18 Access rights; Control 8.3 Information access restriction.

==========

ISO/IEC 27002 requires equipment to be sited and protected in a way that reduces risks from physical and environmental threats. These threats include fire, flood, dust, vibration, electrical interference, unauthorized access, power instability, temperature extremes, and other environmental hazards. Option A is correct because secure siting and protection of equipment are essential to preserving confidentiality, integrity, and availability of information processing facilities. Option B is incorrect because equipment can absolutely be affected by power failures, utility disruptions, voltage fluctuations, overheating, and related events. Option C is incorrect because supporting utilities should be maintained, monitored, and tested as appropriate over time, not only at the beginning. ISO/IEC 27002 physical controls emphasize that technical systems depend on the physical environment. Servers, network devices, storage, and endpoint systems need appropriate location, power, cooling, cabling protection, and resilience measures. Equipment placement should also reduce unauthorized viewing, tampering, theft, and environmental exposure. The verified answer is option A because it reflects the physical protection objective in ISO/IEC 27002. References/Chapters: ISO/IEC 27002:2022, Control 7.8 Equipment siting and protection; Control 7.5 Protecting against physical and environmental threats; Control 7.11 Supporting utilities.

==========