No sign-up needed

Free CISM practice test

20 questions, each with a clear explanation.

Quick PracticeQuestion 1 of 20
Your progress through this set
Information Security GovernanceStep 1 · Choose one answer

A regional credit union hires its first information security manager and asks for a three-year information security strategy. The manager inherits a list of open audit findings and a vendor's proposal for new monitoring tools. What should the manager do first?

Question review

All 20 CISM questions with explanations

Try the set above first, then use this list to review. Each answer and explanation stays closed until you open it.

  1. Question 1 · Information Security Governance

    A regional credit union hires its first information security manager and asks for a three-year information security strategy. The manager inherits a list of open audit findings and a vendor's proposal for new monitoring tools. What should the manager do first?

    1. Start closing the open audit findings in order of their severity
    2. Evaluate the vendor's monitoring proposal against current tools
    3. Learn the credit union's business goals and what shapes them
    4. Adopt a recognized control framework and assess every control in it
    Show answer and explanation for question 1

    Correct answer: C · Learn the credit union's business goals and what shapes them

    ISACA's CISM outline asks managers to identify the internal and external influences on the organization that affect the security strategy, and to keep the strategy aligned with organizational goals and objectives. So the strategy starts from what the credit union is trying to achieve and what bears on it, such as regulation, growth plans, and its threats. Closing audit findings is useful work, but it fixes known gaps rather than setting direction. Judging the vendor's proposal comes later, once the strategy shows what the program needs. A control framework is a helpful reference, yet assessing every control before knowing business priorities spreads effort evenly where risk is not even.

    Look for this next time: An information security strategy starts from the organization's goals and the internal and external factors that affect them.

  2. Question 2 · Information Security Governance

    A retailer's enterprise architecture board maintains a target architecture with approved identity, data, and integration patterns. A product team designs a new customer app with its own separate login store, outside those patterns, and asks the security manager to approve the design. What is the best response?

    1. Align the app's security design with the enterprise architecture before approving it
    2. Approve the design, because the product team owns the decisions about its own application
    3. Approve it once a pre-launch penetration test shows no critical flaws
    4. Hold the app until the board changes the enterprise architecture to fit this design
    Show answer and explanation for question 2

    Correct answer: A · Align the app's security design with the enterprise architecture before approving it

    The current CISM outline adds enterprise architecture and information security architecture, and one of its tasks is to ensure the alignment of security architecture to enterprise architecture. NIST describes security architecture as an embedded, integral part of the enterprise architecture. A separate login store outside the approved identity pattern adds another set of credentials to protect and manage, so the design should be brought into line before approval. Owning the application does not exempt the team from enterprise patterns. A clean penetration test shows that testers found no critical flaws, not that the design fits the architecture. Asking the board to change the architecture for one app reverses the governance relationship.

    Look for this next time: Security architecture is part of the enterprise architecture, so new designs are aligned with it before they are approved.

  3. Question 3 · Information Security Governance

    A security manager wants funding for a privileged access management program. The executive committee approves projects that show how they support business goals. Which submission is most likely to win lasting support from the committee?

    1. A side-by-side comparison of the tool's technical features with two rival products
    2. Industry figures on what peer companies spend on privileged access
    3. A count of the admin accounts found in last month's access review
    4. A business case linking the program to business risks, costs, and benefits
    Show answer and explanation for question 3

    Correct answer: D · A business case linking the program to business risks, costs, and benefits

    ISACA's CISM tasks include developing business cases to support security initiatives and investments, and gaining ongoing commitment from senior leadership. ISACA's glossary describes a business case as the documented rationale for an investment, used to decide whether to proceed and to manage the investment through its life cycle. Linking the program to the business risks it reduces, and to its costs and benefits, speaks to how this committee decides. A feature comparison helps choose a product after the decision is made. Peer spending says nothing about this company's own risk. An account count is useful evidence inside a business case, but on its own it does not show value to the business.

    Look for this next time: Senior leaders fund security through business cases that connect the investment to business risk, cost, and benefit.

  4. Question 4 · Information Security Risk Management

    After a new email filtering control goes live, the residual risk of payment fraud through business email compromise is still rated high. The board's risk appetite statement allows only low risk for payment fraud. What should the security manager do next?

    1. Record the risk as accepted, since a new control has already been put in place
    2. Present further response options to the risk owner to bring the risk within appetite
    3. Propose raising the payment fraud appetite so that it matches the current rating
    4. Wait for next year's annual risk assessment to see whether the rating changes on its own
    Show answer and explanation for question 4

    Correct answer: B · Present further response options to the risk owner to bring the risk within appetite

    ISACA defines residual risk as the risk that remains after management has implemented a risk response, and the CISM outline asks managers to recommend response options that manage risk to acceptable levels based on the organization's risk appetite. The residual rating here is still above what the board allows, so the risk owner needs further options, such as a call-back check before payment details change. Having one control in place does not make the remaining risk acceptable. Raising the appetite to fit a rating defeats the purpose of setting one, and it is the board's decision, not a fix for a control gap. Waiting a year leaves a known gap above appetite.

    Look for this next time: When residual risk still exceeds the risk appetite, the risk owner needs further response options, not a record that calls it accepted.

  5. Question 5 · Information Security Risk Management

    A factory runs a production control system on an operating system that no longer receives security updates. Replacing it would stop a key product line for months. Who should decide whether to accept this risk?

    1. The security manager, who understands the vulnerability best
    2. The IT operations lead, who keeps the system running from day to day
    3. The external auditor, who will review the factory next year
    4. The business owner who is accountable for that production line
    Show answer and explanation for question 5

    Correct answer: D · The business owner who is accountable for that production line

    ISACA's glossary describes the risk owner as the person with the authority and accountability for making risk-based decisions, who owns the loss if the risk is realized, and it says risk acceptance is made according to the risk appetite and tolerance set by senior management. The business owner of the production line carries that accountability here. The security manager's job is to analyze the risk, recommend responses, and make sure the decision is documented. The IT operations lead keeps the system running but does not own the business loss. An external auditor evaluates controls and decisions; making this decision would undermine that independence.

    Look for this next time: The risk owner accountable for the business outcome decides on acceptance, within the appetite senior management sets; security advises.

  6. Question 6 · Information Security Risk Management

    A finance application cannot support the company's new multifactor authentication standard until a vendor upgrade next spring. The finance director asks the security manager to leave the application out of the standard. What is the best approach?

    1. Leave the application out, since the vendor will close the gap in a few months
    2. Block all access to the application until the vendor ships the upgrade
    3. Record a time-limited exception with compensating controls and a review date
    4. Rewrite the standard so that multifactor authentication becomes optional
    Show answer and explanation for question 6

    Correct answer: C · Record a time-limited exception with compensating controls and a review date

    The CISM outline includes establishing and maintaining a security exception process for noncompliance. A documented, time-limited exception records the gap, the compensating controls that lower the risk in the meantime, such as restricted network access and closer monitoring, who approved it, and when it must be reviewed. Quietly leaving the application out leaves the gap unmanaged and easy to forget if the upgrade slips. Blocking all access would stop a business function over a known, temporary gap. Making the standard optional weakens it for every system in order to solve one case.

    Look for this next time: Temporary noncompliance goes through a documented exception with compensating controls, approval, and a review or expiry date.

  7. Question 7 · Information Security Risk Management

    Last year's risk assessment rated the risk of attacks on the company's remote-access gateway as low. This week, a government advisory reports that attackers are actively exploiting a flaw in that gateway model. What should the security manager do first?

    1. Reassess the gateway risk using the new threat information
    2. Keep the low rating until the next annual risk assessment
    3. Replace the gateway vendor as soon as possible
    4. Report the advisory to the board at its next quarterly meeting
    Show answer and explanation for question 7

    Correct answer: A · Reassess the gateway risk using the new threat information

    The CISM outline asks managers to monitor internal and external factors that may require reassessment of risk. Active exploitation of a flaw in the exact product the company uses raises the likelihood behind last year's rating, so the risk should be reassessed now and the response chosen from the result, such as patching or temporary restrictions. Keeping the old rating until the annual cycle leaves it stale while the threat is current. Replacing the vendor may turn out to be a sensible response, but choosing it before reassessing skips the analysis that should drive it. Board reporting may follow, yet a quarterly meeting is too slow as a first step for an active threat.

    Look for this next time: New threat information, such as active exploitation of a product in use, should trigger a risk reassessment rather than wait for the annual cycle.

  8. Question 8 · Information Security Program

    Over two years, a company moved most of its applications to cloud services, and most staff now work from home. Its security architecture still assumes that trusted users sit inside the office network behind a firewall. What should the security manager do?

    1. Add more firewall rules at the office to protect the cloud applications
    2. Update the security architecture for cloud services and remote work
    3. Move the cloud applications back on premises to fit the current design
    4. Keep the current design and retrain staff instead
    Show answer and explanation for question 8

    Correct answer: B · Update the security architecture for cloud services and remote work

    One CISM task is to update the security architecture in accordance with changes to the technology landscape, and information security architecture is a content area ISACA added to the current outline. When both users and applications have left the office network, an architecture built around that boundary no longer shows where protection must happen, so identity, device, and data controls need to be redesigned for the new setup. More office firewall rules do nothing for traffic that never passes through the office. Moving applications back reverses business decisions to suit an outdated design. Awareness helps, but it cannot make up for an architecture that no longer fits.

    Look for this next time: When the technology landscape changes, the security architecture is updated so controls sit where users, data, and applications now are.

  9. Question 9 · Information Security Program

    A company bought a data loss prevention tool to stop sensitive data from leaving by email. During setup, the team cannot say which data is sensitive or where it is stored. What should happen first?

    1. Turn on the tool's default rules and tune them as alerts come in
    2. Block all outgoing attachments until the alert volume is known
    3. Ask every employee to label the files they think are sensitive
    4. Identify and classify information assets, with an owner for each
    Show answer and explanation for question 9

    Correct answer: D · Identify and classify information assets, with an owner for each

    The CISM outline includes establishing and maintaining a process for information asset identification and classification. A data loss prevention tool can only enforce rules about data that has been identified and classified, and NIST describes the information owner as the official responsible for establishing the controls on that information. Default rules guess at what matters and produce alerts that nobody can judge. Blocking every attachment stops normal business and still does not tell the tool what is sensitive. Asking each employee to label files, with no scheme and no owners, gives inconsistent results the tool cannot rely on.

    Look for this next time: Information assets are identified and classified, with owners, before tools such as data loss prevention can protect them well.

  10. Question 10 · Information Security Program

    The information security policy states that sensitive data must be encrypted at rest. Engineering teams ask which algorithms and key lengths are acceptable. Where should these mandatory details be set?

    1. In a security standard that supports the encryption policy
    2. In the policy, revised whenever the details change
    3. In a guideline that teams may follow when it suits their work
    4. In each team's own procedure, written however the team prefers
    Show answer and explanation for question 10

    Correct answer: A · In a security standard that supports the encryption policy

    The CISM outline describes policies that guide the development of standards, procedures, and guidelines, and it treats organizational security standards as documents of their own. In ISACA's glossary, a policy communicates required and prohibited activities, a procedure gives the detailed steps for performing operations in line with standards, and a guideline is less prescriptive than a procedure. Approved algorithms and key lengths are mandatory specifics that sit between the policy's intent and each team's steps, so they belong in a standard. Putting them in the policy would mean revising a high-level, management-approved document for every technical change. A guideline is optional, which does not suit a requirement. Team procedures should apply the standard, not each decide what is acceptable.

    Look for this next time: Policies state intent and rules; standards set the mandatory specifics, procedures give the steps, and guidelines offer optional advice.

  11. Question 11 · Information Security Program

    The board asks the security manager for a quarterly report on whether the information security program is working. Which measure is most useful for this audience?

    1. The number of firewall rule changes the network team made during the quarter
    2. The number of malicious emails the email gateway blocked
    3. The trend in high risks measured against the board's risk appetite
    4. The percentage of servers that received the latest patches
    Show answer and explanation for question 11

    Correct answer: C · The trend in high risks measured against the board's risk appetite

    CISM tasks include evaluating information to report on the effectiveness of the program to senior leadership, and defining management and operational metrics. ISACA's glossary defines a metric as a quantifiable entity that measures the achievement of a process goal, and for a board the goal is risk kept within its appetite. A trend of high risks against that appetite shows whether the program is doing its job. Firewall rule changes and blocked emails measure activity, and a higher count can mean more attacks as easily as better security. Patch percentages are useful operational metrics for IT managers, but they do not tell the board whether business risk is under control.

    Look for this next time: Board reporting uses metrics tied to risk and business goals; activity counts belong in operational reports.

  12. Question 12 · Information Security Program

    A payroll provider that processes employee data plans to move part of its processing to a subcontractor. The company's contract with the provider sets security requirements but says nothing about subcontractors. What is the best way to address this?

    1. Assess the subcontractor only after the provider reports an incident
    2. Amend the contract so requirements flow down and subcontractors need approval
    3. Ask the provider to confirm by email that its subcontractor is secure
    4. End the payroll contract right away and bring all of the processing back in-house
    Show answer and explanation for question 12

    Correct answer: B · Amend the contract so requirements flow down and subcontractors need approval

    The current CISM outline names the management of external services, including nth parties, and its tasks include integrating security requirements into contracts with external parties and monitoring their adherence. Requiring the provider to pass the same requirements on to any subcontractor, and to get approval before using one, keeps the company's protections in force further down the chain. Assessing the subcontractor only after an incident reacts too late. An email assurance is not enforceable and gives no evidence. Ending the contract at once is out of proportion before the gap has been addressed through the contract itself.

    Look for this next time: Security requirements in supplier contracts should flow down to subcontractors, with approval before nth parties are used.

  13. Question 13 · Information Security Program

    A phishing simulation shows that staff in accounts payable click on fake invoice emails far more often than staff in other departments. What should the security manager do next?

    1. Discipline every employee in the department who clicked the link
    2. Stop the simulations, since they are causing tension in finance
    3. Show the yearly company-wide awareness video to everyone again
    4. Train accounts payable on invoice fraud, then run a new simulation
    Show answer and explanation for question 13

    Correct answer: D · Train accounts payable on invoice fraud, then run a new simulation

    The CISM outline includes establishing, promoting, and maintaining an information security awareness training program. Results like these show where the risk sits, so training built around the scenarios accounts payable actually faces, such as fake invoices and changed bank details, addresses the gap, and a later simulation shows whether behavior improved. Disciplining everyone who clicked tends to discourage reporting and does not build the skill. Stopping the simulations removes the measure that found the problem. Repeating a generic video for the whole company spends effort on groups that are not the issue.

    Look for this next time: Awareness results should drive targeted, role-based training, followed by a new measurement.

  14. Question 14 · Information Security Program

    The security team reports that multifactor authentication is now required for remote access, and the project is marked complete. How should the security manager confirm that the control works as intended?

    1. Accept the team's completion report, since the project is closed
    2. Ask a sample of staff whether they now sign in with a second factor
    3. Test every remote-access path for the control, then review the logs
    4. Wait for the next external audit to find out whether it is working
    Show answer and explanation for question 14

    Correct answer: C · Test every remote-access path for the control, then review the logs

    Control testing and evaluation is a subtopic of the current CISM outline, and its tasks include determining whether controls are appropriate and effectively manage risk to an acceptable level. Testing each remote-access path, including older ones such as a legacy VPN, and checking sign-in logs for bypasses gives evidence that the control operates everywhere it should. A completion report shows that the project ended, not that the control works. Asking staff gives impressions and misses paths they never use. Waiting for an external audit leaves any gap open for months.

    Look for this next time: A control is confirmed through testing and evidence, not through a project's completion status.

  15. Question 15 · Incident Management

    In a ransomware exercise, the security team and the business continuity team each claimed the authority to decide when to switch to the recovery site. Their plans had been written separately. What should the security manager do?

    1. Align the incident response plan with the continuity and recovery plans
    2. Give the security team the final say over every recovery decision
    3. Keep the two plans separate so that each team can still act independently
    4. Retire the continuity plan, since incident response covers ransomware
    Show answer and explanation for question 15

    Correct answer: A · Align the incident response plan with the continuity and recovery plans

    One CISM task is to establish and maintain an incident response plan in alignment with the business continuity plan and the disaster recovery plan. The exercise exposed overlapping authority, so the plans need agreed hand-off points and escalation rules that say who decides what, and when. Giving the security team the final say over every recovery decision ignores the continuity team's role in restoring operations. Keeping the plans separate preserves the conflict the exercise found. Incident response does not replace continuity planning, because restoring business operations goes beyond handling the security incident itself.

    Look for this next time: Incident response, business continuity, and disaster recovery plans need aligned triggers, roles, and hand-offs.

  16. Question 16 · Incident Management

    Analysts at a hospital escalate security events inconsistently: one sends a single failed login to the CIO, while another logs a confirmed data leak as low priority. What would most improve consistency?

    1. Escalate all events to the CIO so nothing slips
    2. Define impact-based severity levels, each with its own escalation path
    3. Let each analyst rate severity using their own experience and judgment
    4. Buy a monitoring tool that produces fewer alerts for analysts each day
    Show answer and explanation for question 16

    Correct answer: B · Define impact-based severity levels, each with its own escalation path

    The CISM outline includes establishing and maintaining an information security incident classification and categorization process. Severity levels defined by business impact, such as patient safety, data exposure, and service disruption, each tied to an escalation path, let different analysts reach the same decision about the same event. Sending everything to the CIO buries real incidents in noise. Relying on each analyst's experience is what produced the inconsistency. A tool that produces fewer alerts may lighten the workload, but analysts would still rate the remaining events differently.

    Look for this next time: Defined, impact-based severity levels tied to escalation paths make incident handling consistent.

  17. Question 17 · Incident Management

    Monitoring shows ransomware encrypting files on three file servers, and the activity is still spreading. The incident has been confirmed. What should the incident response team do first?

    1. Restore all three servers from last night's backups as quickly as possible
    2. Run a full root-cause analysis to find how the attackers got in
    3. Isolate the affected servers to stop the spread, preserving evidence
    4. Tell all customers their data may have been exposed
    Show answer and explanation for question 17

    Correct answer: C · Isolate the affected servers to stop the spread, preserving evidence

    ISACA's glossary defines containment as actions taken to limit exposure after an incident has been identified and confirmed, and the CISM outline's incident handling task names containment along with notification, escalation, eradication, and recovery. With encryption still spreading, isolating the affected servers limits the damage, and doing it in a way that keeps evidence supports the investigation. Restoring from backup while the attacker may still have access risks the restored servers being encrypted again. Root-cause analysis matters but comes once the spread has stopped. Decisions about notifying customers follow the communication plan and the facts the investigation establishes, not the first minutes of an incident.

    Look for this next time: Once an incident is confirmed and spreading, containment comes first to limit the damage, ideally while preserving evidence.

  18. Question 18 · Incident Management

    A business impact analysis finds that online order processing can be down for at most four hours before serious harm, while payroll can be down for five days. Both systems fail in the same outage. Which should the recovery plan restore first?

    1. Online order processing, because its tolerable downtime is shorter
    2. Payroll, because employees must be paid before any customer orders
    3. Whichever of the two systems the IT team can restore more quickly
    4. Both systems in parallel, with the recovery staff split equally
    Show answer and explanation for question 18

    Correct answer: A · Online order processing, because its tolerable downtime is shorter

    ISACA's glossary says a business impact analysis prioritizes the recovery of processes and their supporting systems, and NIST describes maximum tolerable downtime as how long a process can be disrupted without significant harm. Order processing reaches serious harm in four hours and payroll in five days, so order processing comes first. Payroll matters, but the analysis shows it can wait longer without serious harm. Restoring whatever IT can fix fastest ignores the business impact the analysis measured. Splitting staff equally slows the recovery of the process with the tighter limit.

    Look for this next time: Recovery priorities come from the business impact analysis: the process with the shortest tolerable downtime is restored first.

  19. Question 19 · Incident Management

    A company has just finished its first incident response plan. Managers want to check that people understand their roles before investing in a larger test, without disrupting operations. Which test fits best?

    1. A full interruption test that shuts down the primary data center
    2. An unannounced red team attack on the live production systems
    3. A yearly review of the plan document by the security team alone
    4. A tabletop exercise that walks key staff through a realistic scenario
    Show answer and explanation for question 19

    Correct answer: D · A tabletop exercise that walks key staff through a realistic scenario

    The CISM outline includes testing and reviewing incident management plans at planned intervals, and it names table-top exercises, simulations, and walk-throughs. NIST describes a tabletop exercise as a discussion-based exercise in which people with roles in a plan talk through their responses to a scenario presented by a facilitator. That checks whether people understand their roles without touching operations, which suits a new plan. A full interruption test risks a real outage and is premature. An unannounced red team attack tests defenses, not whether staff know the plan. A document review by the security team alone never involves the other people who must act.

    Look for this next time: A tabletop exercise is a low-disruption first test of whether people know their roles in a new plan.

  20. Question 20 · Incident Management

    Attackers used stolen passwords to take over 40 customer accounts. The team reset the accounts and closed the incident ticket the same day. What should the security manager make sure happens next?

    1. A search for the analyst whose shift missed the first signs of the attack
    2. A post-incident review of root cause, lessons learned, and risk
    3. An immediate purchase of a new fraud detection tool for customer logins
    4. A ticket note saying all accounts were reset
    Show answer and explanation for question 20

    Correct answer: B · A post-incident review of root cause, lessons learned, and risk

    The CISM outline includes conducting post-incident reviews to support continuous improvement, including root-cause analysis, lessons learned, corrective actions, and reassessment of risk. Resetting the accounts fixed the symptom; the review asks why stolen passwords worked, for example whether multifactor authentication or login rate limits were missing, and decides what changes. Searching for someone to blame discourages honest reporting and misses process causes. Buying a tool before the cause is known may not address it. A note that the accounts were reset records the cleanup, not what the organization learned.

    Look for this next time: A post-incident review turns an incident into corrective actions through root-cause analysis, lessons learned, and risk reassessment.

Use the sample well

The rationale matters more than the score.

A short set can show you what deserves another look. A strong run shows you can read a security management scenario and pick the answer an information security manager would defend: the one that serves the business, its risk appetite, and the program. Twenty questions are a small sample, so the result does not predict a 450 on ISACA's 200–800 scale.

01

Answer before reviewing

Choose the one best answer for the scenario as written. Then read why each other option falls short.

02

Read every rationale

Confirm why the best option fits, even when you were right.

03

Follow the pattern

Use recurring misses—not one score—to choose your next focus.