A hospital requires removable-media encryption, but the rule sits in an optional guideline. If you rename it a standard, are the drives now encrypted? This lesson covers CISA Domain 2, Section 2.3: how policies provide direction, how standards and procedures make it operational, and how guidelines support judgment.
Whatever the document, it must reflect current obligations and risk, be approved at the appropriate level, and reach the people expected to follow it.
2.3.1 Policies
A policy states approved intent, principles and expectations. It should identify its purpose, scope, accountable owner, responsibilities, compliance expectations and review arrangements. Approval comes from the authority established by enterprise governance, often the board or senior management, depending on the policy.
A security policy establishes how the enterprise intends to protect information. Supporting topic policies can address access, acceptable use, data handling, remote work and supplier services. Communicate policies, train affected staff, track acknowledgments where appropriate, and manage exceptions through explicit authority and review dates.
Reviewing the information security policy
The IS auditor checks business alignment, legal obligations, ownership, scope, enforcement and exception handling, and confirms that significant changes in cloud use, data processing, remote access or threat exposure prompt reconsideration.
Exam trap: a recently approved document can still be inadequate if important activities are outside its scope.
The five document types
| Document | Purpose | Example |
|---|---|---|
| Policy | States intent and expectations | Sensitive customer information must be protected from unauthorized disclosure |
| Standard | Specifies a mandatory requirement | Approved strong authentication is required for privileged remote access |
| Baseline | Defines an approved minimum configuration or control level | The server build disables unnecessary services and applies the required logging settings |
| Procedure | Describes the steps and responsibilities for a task | Verify approval, provision the role, test access and record completion |
| Guideline | Recommends ways to act where judgment is appropriate | Suggested wording for clear data handling instructions |
2.3.2 Standards
An internal standard turns policy direction into a specific mandatory rule. It should be measurable and suitable for the systems it governs. A baseline is a minimum approved level, often expressed as a standard configuration for a platform or class of assets.
Exceptions to a standard require a risk assessment, approval, compensating measures where needed, and expiry or review.
2.3.3 Procedures
A procedure states how a task is performed, who performs it, what approvals are needed, and which records demonstrate completion. It should be usable by trained staff and match the actual process. Outdated instructions can create errors even where the policy and standard remain sound.
2.3.4 Guidelines
A guideline recommends practices and supports consistent judgment. It is generally advisory unless the enterprise explicitly makes a requirement mandatory through another instrument. Terminology can vary, so inspect the organization's own definitions and approval arrangements.
Don't force the five document types into a rigid chronology: guidelines can support several levels, and a baseline commonly sits within standards.
Example: a new classification program first needs its objectives, approved scheme, ownership and handling requirements understood, and a discovery tool can then support implementation. If the scheme already exists and the question asks how to locate unclassified files, "write a policy" again may not address the actual gap.
Making exceptions accountable
Translate direction into rules people and systems can implement, with owners, approval, communication, monitoring and review. An exception process needs:
- the reason and affected scope
- a risk assessment and compensating measures
- an authorized decision
- an expiry date and reassessment
An exception is a managed departure, not permission to ignore external obligations or unlimited acceptance of risk.
Hospital example: a mandatory standard establishes the encryption requirement, while deployment, monitoring, training and exception handling make it effective. Renaming the document does not encrypt the drives. Sample actual devices and permitted exceptions, compare them with the approved rule, and verify that obsolete versions are withdrawn and that contractors and automated services receive the requirements relevant to their work.
Expired exception: a legacy application has an approved six-month exception to a mandatory access standard. Nine months later it is still open and the alternative review has stopped. Examine the approved scope, expiry, decision authority and required alternate safeguard, and test whether the safeguard operated during the authorized period. The finding should distinguish the original authorized exception from the exposure after expiry, and identify the responsible decision maker.
Practice questions
1. The information security policy was approved three months ago but does not cover a new cloud service that processes customer data. What is the BEST conclusion?
Answer: the policy may be inadequate because cloud use is outside its scope. Recent approval does not make a policy adequate.
2. Management has an approved classification scheme and asks how to find files that were never classified. What is the BEST recommendation?
Answer: use a discovery tool to locate the unclassified files. Writing another policy does not address the actual gap.
Keep going
- Read the free companion book, the CISA Complete Study Guide by Muhammad Aamir.
- Watch the full CISA Complete Course by Mirak X. Next up is Section 2.4, Enterprise Architecture.
- Subscribe to Mirak X on YouTube. New lesson every day at 6 PM (PKT).
- Try free CISA practice questions and mock exams at https://certprepx.com/.
Free study material. Not affiliated with or endorsed by ISACA. CISA is a registered trademark of ISACA.


