During the Act phase, the organization takes corrective and improvement actions to maintain and continually improve the ISMS.

Management should define and approve an information security policy to provide appropriate direction and support for information security in line with organizational objectives.

Risk assessment combines all three activities: identifying risks, analyzing their likelihood and impact, and evaluating them against risk criteria.

Under Control 5.1, information security policies should include statements that define direction, responsibilities, and policy expectations, including how exemptions and exceptions are handled. Exception handling is important because policies cannot be treated casually or bypassed informally. When an exception is necessary, it should be justified, approved, documented, time-bound where appropriate, risk-assessed, and reviewed. This preserves governance and ensures deviations do not become uncontrolled weaknesses. Option A, recovery from a data breach, is important but belongs more naturally to incident management, business continuity, and response planning rather than the general information security policy statement. Option C, procedures for using automated information systems, may be addressed in acceptable use or operational procedures, but it is not the best match for Control 5.1's policy content. The information security policy establishes the authority and framework for topic-specific policies and procedures. It should include high- level statements on objectives, principles, responsibilities, compliance expectations, and exception management. Therefore, option B is verified. References/Chapters: ISO/IEC 27002:2022, Control 5.1 Policies for information security; Control 5.36 Compliance with policies, rules and standards for information security; Control 5.37 Documented operating procedures.

Control 7.4 falls under the physical controls theme, requiring premises to be continuously monitored for unauthorized physical access.