156-110 Practice Questions

Mandatory sign-on describes the authentication approach where users must log in individually at each server and access control point, requiring separate authentication for each system without credential sharing or centralized authentication mechanisms. This represents a decentralized authentication model that provides isolated security but increases administrative overhead and user inconvenience. Role-based access control manages permissions not authentication methods, three-factor authentication refers to the number of authentication factors used, single sign-on allows one login for multiple systems (the opposite of this scenario), and hybrid access control describes permission models rather than authentication approaches.

Smart cards, access control lists, authentication servers, and auditing represent technical controls that use technology-based mechanisms to enforce security policies and protect information assets. Technical controls are implemented through hardware, software, and firmware solutions to automate security functions and provide consistent enforcement. Administrative controls involve policies and procedures, physical controls protect against physical threats, role-based and mandatory controls describe access control models rather than control categories.

Procedures should be evaluated whenever business processes are modified because changes in business operations can impact security requirements, introduce new risks, or make existing procedures obsolete or inadequate. Process modifications often require procedural updates to maintain security effectiveness and operational alignment. New user onboarding, anniversaries, regular usage, and exploit discoveries may trigger procedure reviews but don't represent the systematic evaluation trigger that ensures procedures remain relevant to actual business operations.

External intrusion attempts are attacks originating from outside the organization's network perimeter, where unauthorized external entities attempt to gain access to internal resources without proper permissions or rights. This represents the classic security threat model where attackers from the internet or other external sources try to breach network defenses. The other options incorrectly describe internal threats (insider attacks), confused definitions mixing external users with legitimate public access, nonsensical vulnerability exploitation for access removal, or internal misuse of authorized access.

Business Continuity Plans must be integrated with change-control processes because any organizational changes (infrastructure, personnel, procedures, technology) can impact business continuity requirements and recovery capabilities. Change control ensures BCP updates are evaluated and implemented systematically when organizational changes occur. Disaster recovery is a component of BCP, not the integration point; inventory maintenance, discretionary budgets, and compensation reviews are operational processes that don't directly govern BCP maintenance cycles.

Connectivity failures, hardware failures, and utility failures represent the three primary infrastructure-related failure categories that Business Continuity Plans must address. These cover network connectivity disruptions, physical equipment malfunctions, and power/utility service interruptions that can halt business operations. Accounting failures and personal failures are operational issues that, while important, are not among the core infrastructure failure types that form the foundation of most BCP scenarios in Check Point security planning.

Hardware failures, along with connectivity and utility failures, represent core infrastructure failure categories that Business Continuity Plans must address. Physical equipment failures including servers, storage systems, network devices, and workstations can completely disrupt business operations and require specific recovery procedures. Accounting failures and personal failures, while operational concerns, are not among the primary infrastructure-based failure scenarios that BCPs are designed to handle in enterprise security frameworks.

Utility failures, including power outages, heating/cooling system failures, and telecommunications service disruptions, are fundamental infrastructure threats that Business Continuity Plans must address alongside connectivity and hardware failures. These utility disruptions can render facilities unusable and systems inoperable, requiring backup power, alternative locations, and service restoration procedures. Accounting and personal failures are procedural issues that don't constitute the primary infrastructure failure categories central to BCP design.