Short · Executive leadership · 17 min read
The CISO Just Resigned: How to Keep Security Decisions Working
When your CISO resigns, establish who can make consequential security decisions, preserve the evidence those decisions require, and verify that the organization can operate without the departing person's access or assistance. Do those things alongside the replacement search. A named interim owner is useful only when the authority, information, technical access and available support make the appointment executable.
I would treat the departure as a controlled transfer of decision capability. The transition is complete when the receiving organization can perform the required work and the departing person's obsolete authority and access have been removed. A signed handover document can support that conclusion; it cannot establish it by itself. The practical test is whether the next important decision can move from evidence to authorized action without an undocumented dependency on the former CISO.
This paper develops a proposed acceptance method for that transfer. It synthesizes governance, personnel security, identity, contingency and configuration-management guidance. It is not an empirical study of CISO departures, a legal opinion or a claim that every vacancy requires the same response. The worked case is fictional. The distinct question is how to make an actual departure survivable; choosing the long-term employment model is a separate decision.
Separate the vacancy from the replacement search
The first distinction is between continuity and succession. GAO's Green Book separates long-term replacement planning from contingency arrangements for sudden personnel changes, including assignment of responsibilities when a key role becomes vacant without notice (U.S. Government Accountability Office [GAO], 2025, §§4.06–4.08). That is a federal internal-control standard. I use its distinction as an organizational design principle, not as a requirement imposed on every private employer.
A replacement search asks which leader the organization needs. A vacancy response asks which decisions cannot wait for that search. Those questions have different evidence and acceptance criteria. A capable candidate may not be available when a risk exception expires tomorrow. A suitable interim sponsor may keep urgent decisions moving without being the right permanent executive. Treating either appointment as the entire solution conceals the work between them.
Start with the departure conditions. Has notice been given, has employment already ended, or is the leader moving to another role? Can the person assist with a bounded handover? Is there an active incident, unresolved integrity concern or immediate safety issue? Coordinate the personnel process with the appropriate HR, legal and operational owners. A resignation alone is not evidence of misconduct; a credible compromise concern requires its own response and should not be disguised as routine transition administration.
I would avoid universal promises about recovering in thirty days or the cost of a hurried hire. The transition window follows the actual obligations and dependencies. A cooperative departure with documented delegation is different from a sudden absence during a live investigation. Both need evidence of continuity, but the sequencing and available options can differ sharply.
Make the interim appointment executable
NIST CSF 2.0 calls for cybersecurity roles, responsibilities and authorities to be established, communicated, understood and enforced, with adequate resources allocated to the strategy and responsibilities (National Institute of Standards and Technology [NIST], 2024, GV.RR-02–03). The distinction between naming a role and enforcing its authority is particularly useful during a vacancy. An executive announcement may identify the owner while leaving purchasing, service interruption and risk acceptance assigned elsewhere.
For each consequential decision, identify the accountable business authority, the security adviser, the person who can execute it and an available alternate. These may be different people. The interim security lead should not automatically become the owner of every business risk, the incident commander, the legal notification authority and the administrator of every platform. Where responsibilities are combined, record the combination deliberately and examine the capacity it requires.
Give the interim mandate a defined scope, effective time, review point and escalation route. State which decisions remain reserved to executives or the governing body. Confirm access to the evidence required for decisions within scope. Check that operational teams and relevant providers recognize the arrangement. A delegation that exists only in the sponsor's email cannot reliably resolve a refusal by an external service desk that still recognizes the departed leader as its sole authorized contact.
Capacity must be part of the appointment. If an engineering manager takes interim responsibility, identify which existing work is reassigned or deferred. Adding a title to an unchanged workload is a proposal about capacity, not proof of capacity. I would review the urgent queue with the receiving owner and identify decisions they cannot support without specialist advice, additional execution resources or a different authority path.
Inventory unfinished decisions before collecting documents
A document archive is useful, but an unresolved-decision inventory is a better starting point for continuity. Ask what will require a decision before the next review, what consequence follows if it is missed and where the supporting evidence lives. Include open investigations, expiring exceptions, scheduled changes, supplier commitments, remediation acceptance and deadlines already communicated outside the security team.
For each item, preserve the current state, the next decision, the responsible parties, the due condition, the evidence location and the most important uncertainty. Record whether the deadline is contractual, operational, internally proposed or still being verified. A date copied from a presentation should not silently become an established obligation. Conversely, an unresolved contractual question should receive an owner and a near-term review rather than disappear because nobody has confirmed its consequences.
I would reconcile at least three views: the departing leader's account, the systems of record and the people who must act next. The outgoing CISO may remember a commitment that never entered the risk register. The ticket system may show a remediation as complete even though its business owner has not accepted it. A supplier may be awaiting an approval that internal records describe as already given. Preserve disagreements until the relevant evidence resolves them.
That process also protects against an unfair handover. Distinguish an inherited issue from a new failure during the transition. Preserve earlier decisions and assumptions rather than rewriting the record to make either leader look better. A receiving executive should be able to say which conditions were known at transfer, which were uncertain and which changed afterward. Accountability becomes more useful when the chronology remains intact.
Treat authority, access and evidence as separate dependencies
I would map each urgent decision as a small dependency chain: evidence must be accessible, a competent person must interpret it, an authorized person must decide, and an authorized operator must execute. The relevant provider or system must recognize that operator. The transition can fail at any link even when the organization chart looks complete.
This is a proposed diagnostic model, not a numerical maturity score. Consider a risk exception whose approver is available but whose supporting assessment is stored in the former CISO's restricted workspace. Authority exists; evidence access does not. Consider an emergency supplier engagement for which the analyst has a valid portal account but no spending authority. Technical access exists; permission to commit the organization does not. Different deficiencies require different repairs.
A compact transfer record makes these distinctions inspectable:
| Dependency | Evidence of transfer | Failure that remains possible |
|---|---|---|
| Decision authority | Current delegation with scope and alternate | Delegate cannot approve this consequence |
| Information | Receiving owner can retrieve the relevant record | Record is accessible but incomplete or stale |
| Execution | Named operator can perform the bounded action | Required downstream approval is missing |
| External recognition | Provider confirms the authorized contact | Another supplier workflow uses an old contact |
| Continuity | Substitute completes a defined exercise | Exercise omitted a consequential condition |
| Retirement | Obsolete access and authority are addressed | Uninventoried sessions or recovery paths remain |
Do not average these rows into a reassuring percentage. A missing prerequisite for a consequential decision can matter more than many successful administrative transfers. Report the failed dependency, the affected decision and the available fallback. This lets the executive choose a repair with an explicit consequence rather than approve a transition described only as mostly complete.
Revoke the person's access without losing the organization's capability
NIST SP 800-53's personnel-termination control combines disabling access and revoking associated authenticators with retaining organizational access to information and systems previously controlled by the departing individual. Its personnel-transfer control calls for reviewing and modifying access when duties change (Joint Task Force, 2020, PS-4–PS-5). The combined lesson is important: removal and continuity are related requirements, not interchangeable checkboxes.
I would separate personal accounts, role-based permissions, shared secrets, machine identities and recovery mechanisms. A named human account should not be handed to the successor as a shortcut. Establish the receiving person's approved identity and appropriate access, preserve attribution and remove obsolete permissions according to the actual departure conditions. Where an urgent compromise concern requires immediate revocation, use an independently authorized recovery path; do not delay containment merely to finish a convenient knowledge-transfer meeting.
Inspect access beyond the primary identity directory. Relevant examples include security management consoles, cloud accounts, source repositories, domain administration, password vaults, incident-provider portals and approval workflows. This is a discovery list, not an assertion that every CISO holds those permissions. The actual inventory should come from assigned access, system owners and observed dependencies rather than assumptions about the title.
Revocation also needs attention to sessions and tokens. NIST's authentication guidance distinguishes application sessions from identity-provider sessions and notes that access and refresh tokens can outlast an authentication session (Temoshok et al., 2025, §5). Disabling a central identity therefore should not be treated as universal proof that every downstream capability has ended. Verify the relevant application's behavior and document what has actually been invalidated, what expires later and what remains uncertain.
Change custody carefully when secrets and keys are involved
“Rotate everything” sounds decisive but is not an adequate migration design. First identify what the outgoing person could use, what the organization needs to retain and which consumers depend on each credential. A password, a signing key, a data-decryption key and a recovery factor do not have the same lifecycle. Removing the former user's authorization is not always the same operation as replacing the underlying secret.
NIST's key-management guidance distinguishes deactivated keys from compromised keys and explains that some deactivated keys may still be needed to process previously protected information, including archived data (Barker, 2020, §§7.4–7.5). The source does not say that a resignation makes every key compromised. It supports making a deliberate decision about key purpose, state and remaining use rather than destroying material indiscriminately.
For a hypothetical shared service credential, I would identify its consumers, create an approved replacement, update those consumers, test the intended operation and retire the old credential under a controlled change. For a historical decryption requirement, I would examine protected custody and authorized recovery before altering key availability. The exact method belongs to the relevant platform and cryptographic design; this is a sequencing argument, not a vendor-specific rotation procedure.
NIST's configuration-management guide says that emergency changes still need management and control, with review as soon as practical when the ordinary process cannot be completed beforehand (Johnson et al., 2011, §3.3.2). Apply that principle to urgent credential changes. Record what changed, why, who authorized it, how service operation was checked and what follow-up remains. An emergency can justify an abbreviated sequence; it does not make an undocumented service failure evidence of successful security.
For the implementation work, use the separate SaaS offboarding verification method to test effective access removal and the exposed-secret rotation analysis where compromise is suspected. The leadership handover should assign and accept those technical tasks, without treating an ordinary departure as evidence of a leak.
Preserve the ability to investigate and respond
A leadership departure should not pause an existing incident process. NIST SP 800-61 Rev. 3 places incident responsibilities across the organization and, where relevant, third parties; it recommends documenting those responsibilities and granting the authority needed to fulfill them (Nelson et al., 2025, GV.RR-02). The transition task is to verify that the documented arrangement still works after the personnel change.
For an active investigation, identify its operational lead, evidence custodian, authorized decision makers and external advisers. Confirm which facts remain unverified, which actions are already approved and when the next consequential decision is due. Avoid creating a second command chain merely because an interim executive has joined. Existing responders need clarity about what has changed and which authorities remain in effect.
Preserve relevant records through the organization's authorized retention and investigation processes. Do not export an entire mailbox into a broad transition folder simply because some messages may matter. Locate necessary business records, apply appropriate access restrictions and involve the responsible legal or privacy function when scope is uncertain. This is a proposed handling discipline, not a claim about a universal retention period or the legal status of particular communications.
Test the contact path under a controlled scenario. Can the incident lead reach the current decision authority and alternate? Can an external responder validate the new caller's authority without contacting the former employee? If not, record the specific failure and a workable temporary route. A successful test establishes only the path and conditions exercised; it does not certify the full response program.
Reconfirm supplier relationships and external commitments
A supplier relationship contains more than a contact name. Distinguish authority to request technical assistance, approve additional charges, change service scope and receive restricted information. One individual may previously have held several of those powers. The receiving organization needs to know which have been reassigned, which require contractual action and which the provider has actually acknowledged.
NIST's supply-chain guidance calls for documented access agreements for contractors and other external personnel, including appropriate access methods and levels, review mechanisms and updates when personnel change (Boyens et al., 2024, PS-6). That is especially relevant when interim leadership is supplied externally. Do not give a new adviser unrestricted access merely because the organization is under time pressure. Define the work, provide the required access and maintain the ability to withdraw it.
I would also create a targeted commitment review with the appropriate legal, procurement and compliance owners. Identify documents that name an individual, require a designated role, restrict delegation or contain change-notification terms. Record the applicable provision, its owner and the action determined from it. This paper does not establish which regulation, contract or insurer requires a particular notice; neither universal notification nor universal silence is a defensible default.
Internal and external messages should reflect verified coverage. If an interim appointment is effective but a provider has not recognized its authority, do not describe the transition as complete. Explain the limited gap to those who need to manage it, using approved communications. The purpose is to preserve operating confidence through accurate statements, not imply that every customer needs the same personnel announcement.
Keep the monitoring and maintenance cycle alive
The absence of new incident reports is weak evidence of continuity if nobody can show who is reviewing the reporting channel. NIST SP 800-137 describes continuous monitoring as ongoing awareness supporting risk decisions, with assessment frequency sufficient for those decisions rather than literal uninterrupted measurement (Dempsey et al., 2011, p. 1). I would preserve the decision cycle that makes monitoring useful, not merely the tools producing its output.
Name who reviews alerts, exceptions, control failures and overdue actions during the interim period. Check both the underlying evidence and the delivery path. A dashboard can refresh while its alert mailbox has no owner. A remediation report can arrive on time while nobody is authorized to accept the result. Make those dependencies explicit before interpreting a quiet reporting period as a stable security posture.
Contingency documents need corresponding maintenance. NIST SP 800-34 Rev. 1 calls for plans to reflect organizational changes and for review of personnel and vendor contacts, supporting agreements and related operating information (Swanson et al., 2010, §3.6). That guidance concerns federal information-system contingency plans; the narrower application here is to refresh the records affected by the departure and verify their distribution.
I would prioritize updates by consequence. Fix an obsolete incident escalation contact before polishing a general organization chart. Update the authoritative record, identify distributed copies that can still influence action and confirm that recipients know which version applies. A new document in the transition folder does little if the provider's runbook still points to a person who has left.
Give the team a manageable interim arrangement
The departing executive's job description may hide several different kinds of work. NICE distinguishes work roles from job titles and describes roles through tasks with associated knowledge and skills (Petersen et al., 2020, §3.4). That distinction helps avoid asking one interim appointee to absorb an undefined bundle of technical, managerial and governance responsibilities.
Break the vacancy into work that must continue, decisions that need a different authority and improvements that can be deferred with an explicit consequence. Discuss the allocation with the people doing it. An analyst may be well placed to maintain an investigation record while needing a separate sponsor for a business interruption. A deputy may understand the program but lack the capacity to retain every previous responsibility and perform the interim role.
The receiving team also needs a route to disagree with the handover account. Invite specific corrections about missing evidence, unowned work and dependencies that the leadership summary overlooks. Preserve those corrections without treating them as disloyalty to either leader. I would ask what the proposed arrangement makes harder to do, then adjust the allocation rather than assuming the announcement has settled the operating model.
Avoid turning an independent reviewer into the default replacement without examining the consequences. The IIA's Three Lines Model distinguishes management responsibilities from independent internal audit and identifies the loss of independence when assurance covers activities for which the function has management responsibility (Institute of Internal Auditors [IIA], 2024, pp. 5, 11). Interim operational work may be necessary, but the assurance arrangement must reflect it honestly and provide an appropriate separate review where needed.
Work through a fictional transfer failure
Consider fictional Northbridge, whose CISO leaves with a short notice period. Three items require attention: an incident-response retainer renewal, a risk exception awaiting a decision and a scheduled recovery exercise. The COO is named interim sponsor, the security manager leads operations and a consultant is available for specialist advice. None of those appointments, by itself, establishes that the three items can progress.
In the invented scenario, the supplier portal still names the departing CISO as the only commercial approver. The risk assessment is accessible, but its latest exception conditions exist only in a restricted message thread. The recovery exercise assumes access to an emergency credential whose recovery factor is assigned to the departing person's device. These are different failure modes: external authority recognition, incomplete decision evidence and a technical recovery dependency.
I would repair them through separate owners. Procurement obtains documented recognition of the current commercial authority. The authorized record custodian reconciles the exception conditions into the controlled decision record. The platform owner establishes an approved recovery arrangement, verifies access under the permitted test conditions and removes the obsolete factor. None requires granting the consultant every administrative permission or leaving the former account active indefinitely.
Now run a bounded receiving-team exercise without the departing CISO narrating the answers. The sponsor should identify the renewal decision and its scope. The security manager should reconstruct the exception's current conditions and route it to the right owner. The platform team should demonstrate the agreed recovery step. If one test fails, the transition record retains that gap, its consequence and a temporary control rather than awarding a blanket completion label.
Suppose the first two pass but recovery depends on a second unrecognized factor. The useful outcome is discovery of a specific unresolved dependency. It is not “two-thirds secure.” The numbers here count invented tasks, not measured risk reduction or the probability of surviving an incident. The case demonstrates how separating the dependencies changes the repair; it supplies no evidence about typical CISO departures.
Close the handover through acceptance, not elapsed time
I would agree a small set of consequential acceptance cases before declaring the transition complete. Choose them from the unfinished-decision inventory and the changed access paths. For each, specify the expected outcome, permitted test conditions, evidence collected, observed result and remaining limitation. Have the receiving owner explain the decision from the record rather than repeat the departing person's presentation.
Closure should require an explicit disposition for unresolved items. Some can remain open with a defined temporary arrangement and accountable owner; some prevent a consequential capability from being claimed at all. A missing nonessential historical document is not equivalent to an unavailable emergency decision authority. Explain the distinction in the handover acceptance instead of demanding artificial perfection or accepting every exception under a generic risk statement.
A reasonable objection is that this process could become excessive bureaucracy during a short departure window. It can. The remedy is to prioritize actual decisions and use existing systems of record, not create a parallel archive of everything the security team has ever done. Another objection is that rehearsals can create false confidence. Record the exercise boundary and test a material dependency; do not generalize a tabletop success into proof of production recovery.
The source base supports the component practices, not a validated universal handover algorithm. Organizations differ in scale, criticality, available deputies and applicable obligations. My synthesis cannot establish that a vacancy is safe, that a particular interim leader is qualified or that all undiscovered dependencies have been eliminated. Its value is a more inspectable decision about what can continue, what remains exposed and who is responsible for the next repair.
Once immediate continuity is established, use the separate full-time versus fractional CISO decision framework to evaluate the enduring arrangement. If a live event requires decisions beyond standing authority, the crisis activation analysis addresses that different task. Neither question should delay a necessary transfer of access, evidence and decision ownership today.
Request a security leadership transition briefing if you need to establish the interim mandate, identify the consequential handover gaps or define acceptance before the outgoing leader leaves. Start with a sanitized description of the decisions at risk and the time available. The useful deliverable is an operating arrangement the receiving team can demonstrate, with its limits visible—not another title on an organization chart.
References
- Barker, E. (2020). Recommendation for key management: Part 1—General (NIST Special Publication 800-57, Part 1, Rev. 5). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-57pt1r5
- Boyens, J., Smith, A., Bartol, N., Winkler, K., Holbrook, A., & Fallon, M. (2024). Cybersecurity supply chain risk management practices for systems and organizations (NIST Special Publication 800-161, Rev. 1, Update 1). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-161r1-upd1
- Dempsey, K., Chawla, N. S., Johnson, A., Johnston, R., Jones, A. C., Orebaugh, A., Scholl, M., & Stine, K. (2011). Information security continuous monitoring (ISCM) for federal information systems and organizations (NIST Special Publication 800-137). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-137
- Institute of Internal Auditors. (2024). The IIA's Three Lines Model: An update of the Three Lines of Defense (September 2024 update). https://www.theiia.org/globalassets/documents/resources/the-iias-three-lines-model-an-update-of-the-three-lines-of-defense-july-2020/three-lines-model-updated-english.pdf
- Johnson, A., Dempsey, K., Ross, R., Gupta, S., & Bailey, D. (2011). Guide for security-focused configuration management of information systems (NIST Special Publication 800-128; updated October 10, 2019). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-128
- Joint Task Force. (2020). Security and privacy controls for information systems and organizations (NIST Special Publication 800-53, Rev. 5; updated December 10, 2020). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-53r5
- National Institute of Standards and Technology. (2024). The NIST Cybersecurity Framework (CSF) 2.0 (NIST CSWP 29). https://doi.org/10.6028/NIST.CSWP.29
- Nelson, A., Rekhi, S., Souppaya, M., & Scarfone, K. (2025). Incident response recommendations and considerations for cybersecurity risk management: A CSF 2.0 community profile (NIST Special Publication 800-61, Rev. 3). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-61r3
- Petersen, R., Santos, D., Smith, M. C., Wetzel, K. A., & Witte, G. (2020). Workforce framework for cybersecurity (NICE framework) (NIST Special Publication 800-181, Rev. 1). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-181r1
- Swanson, M., Bowen, P., Phillips, A. W., Gallup, D., & Lynes, D. (2010). Contingency planning guide for federal information systems (NIST Special Publication 800-34, Rev. 1; updated November 11, 2010). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-34r1
- Temoshok, D., Fenton, J. L., Choong, Y.-Y., Lefkovitz, N., Regenscheid, A., Galluzzo, R., & Richer, J. P. (2025). Digital identity guidelines: Authentication and authenticator management (NIST Special Publication 800-63B-4). National Institute of Standards and Technology. https://doi.org/10.6028/NIST.SP.800-63B-4
- U.S. Government Accountability Office. (2025). Standards for internal control in the federal government (GAO-25-107721). https://www.gao.gov/assets/gao-25-107721.pdf