The FFIEC's 2015 Management booklet put the CISO's reporting line and IT staffing into examination procedures
The revised Management booklet the FFIEC members issued on November 10, 2015 said the CISO should not report to IT operations management, and its procedures had examiners check the CISO's authority, succession, backups and IT turnover. Organization charts and HR records became examination evidence.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
The revised Management booklet the FFIEC members issued on November 10, 2015 said the CISO should not report to IT operations management, and its procedures had examiners check the CISO's authority, succession, backups and IT turnover. Organization charts and HR records became examination evidence.
- The week Our argument is that the booklet turned organizational design into examination evidence.
- The reporting line moved the CISO away from IT operations A reporting line determines who settles disputes.
- The board's list made oversight specific The booklet then listed what the board or a board committee should do. [2] The list is worth reading as a set of records, because each item implies a document an examiner can request.
- The workforce file became part of the IT risk file In our reading, this part of the booklet widened what an IT leader needed to keep.
- The scale question was answered with alternatives, not exemptions The booklet covered a wide range of institutions. [2] Its definition of "financial institution" ran from national banks to credit unions, and included technology service providers that serve them. [2] The guidance had to make sense for each.
- The limits of guidance, and where rules went further The booklet was examination guidance. [3] Neither the press release nor the OCC bulletin described it as a rule, and the OCC called it guidance. [1] [3] In our reading, its force lay in examination findings and the supervisory responses that follow them.
- With hindsight The FFIEC's other 2015 cybersecurity product had a different fate.
The week
On November 10, 2015, the members of the Federal Financial Institutions Examination Council issued a revised "Management" booklet. [1] The booklet is part of the FFIEC Information Technology Examination Handbook, known as the IT Handbook. [1]
The press release said the booklet, including its examination procedures, had been substantially revised. [1] It said the booklet outlined the principles of sound governance and, more specifically, IT governance. [1] It said the booklet explained how IT risk management related to enterprise-wide risk management and governance. [1]
The release listed what the updated examination procedures would help examiners evaluate. [1] The two areas were IT governance as part of overall governance in financial institutions, and IT risk management as part of enterprise-wide risk management. [1]
It listed three other relevant changes. [1] The booklet incorporated cybersecurity concepts as part of information security. [1] It brought in management-related concepts from other booklets of the IT Handbook. [1] It augmented and further delineated the stages of the IT risk management process: risk identification, measurement, mitigation, monitoring and reporting. [1]
The Office of the Comptroller of the Currency issued OCC Bulletin 2015-44 the same day. [3] The bulletin was addressed to the chief executive officers of national banks, federal savings associations and federal branches and agencies, and to technology service providers, among others. [3] It said the Management booklet was one of 11 that made up the IT Handbook. [3]
The OCC's bulletin included a note for community banks. [3] It said the guidance applied to all national banks and federal savings associations. [3] It said community banks should implement effective IT governance and adopt IT risk management practices commensurate with the level of risk and complexity of their IT operations. [3]
The booklet itself is dated November 2015. [2] Its introduction said it rescinded and replaced the June 2004 version. [2] It said it provided guidance to examiners and explained how IT risk management was a component of risk management, which in turn was a component of governance. [2]
The booklet defined its audience broadly. [2] A footnote said the term "financial institution" included national banks, federal savings associations, state savings associations, state member banks, state nonmember banks and credit unions. [2] It also included technology service providers that serve those entities. [2]
The booklet's main text was organized in three parts: governance, risk management, and IT risk management. [2] Its governance part set out roles for the board of directors, executive management, the chief information officer or chief technology officer, the chief information security officer, IT line management and business unit management. [2] Appendix A carried the examination procedures, organized as objectives for examiners to work through. [2]
The booklet cited earlier FFIEC material on the threat environment. [2] A footnote referred to the FFIEC's "Cybersecurity Threat and Vulnerability Monitoring and Sharing Statement," dated November 3, 2014. [2] The booklet named information sharing networks such as the Financial Services Information Sharing and Analysis Center and the FBI's InfraGard as examples of external resources. [2]
The release and bulletin did not describe the booklet as a new regulation. [1] [3] The OCC called it guidance. [3] Its force came through examinations: the procedures told examiners what to look for when they assessed an institution's management of IT. [2]
The 2015 Management booklet reads at first like a governance primer. [2] Read through its examination procedures, it is something more specific: a description of how an institution's technology function should be staffed and organized, written so that an examiner could check it. [2]
Our argument is that the booklet turned organizational design into examination evidence. It told examiners to check where the chief information security officer reported, whether succession and backups existed for key IT positions, and why IT staff were leaving. [2] Those are workforce and structure questions. The booklet made them part of how an institution's management of technology would be judged. [2]
For a bank or credit union executive, the practical consequence is that the organization chart, the job descriptions and the HR records became part of the IT risk file. The booklet did not prescribe a single structure. [2] It did describe what examiners would ask, and what answers would show weakness. [2]
We take it in five parts, each a different set of questions the booklet put to an institution:
- The reporting line: where the CISO sits, and why the booklet wanted it outside IT operations.
- The board's list: what the board should approve, oversee and receive.
- The workforce file: hiring, succession, backups, turnover and access.
- The scale question: how the booklet allowed for small institutions and service providers.
- The limits of guidance: what the booklet did not require, and where later rules went further.
The reporting line moved the CISO away from IT operations
The booklet's section on the chief information security officer is short and direct. [2] It said the CISO is responsible for overseeing and reporting on the management and mitigation of information security risks across the institution. [2] It said the CISO should be held accountable for the results of that oversight and reporting. [2]
Independence as a reporting question
The booklet framed independence in terms of reporting lines. [2] To ensure independence, it said, the CISO should report directly to the board, a board committee, or senior management, and not IT operations management. [2]
It explained the reason. [2] It said that while cost and benefit decisions will always need to be made, security decisions and funding should not be unduly influenced by operational ease or budgetary constraints. [2] It said the reporting structure should show that the CISO has appropriate authority and should avoid conflicts of interest. [2]
The booklet also described a change in how the role was seen. [2] It said that while the office of the CISO had in the past been considered a technology function, the role had become a strategic and integral part of the business management team. [2] It said the CISO should be an enterprise-wide risk manager rather than a production resource devoted to IT operations. [2]
Why the line matters in daily work
A reporting line determines who settles disputes. When a CISO reports to the head of IT operations, a disagreement over a patch window, a firewall exception or a delayed project is resolved by the person responsible for uptime and delivery. In our reading, the booklet's concern was that this resolution would favor operational ease by default.
When the CISO reports to the board, a board committee or senior management outside IT operations, the same dispute reaches someone who weighs it against the institution's risk appetite. [2] The booklet tied the CISO's authority to decisions in line with the board's risk appetite. [2] The examination procedures asked examiners to determine whether the reporting structure gave the CISO that authority without conflicts of interest. [2]
Three reporting designs and what each trades
The booklet named three places the CISO could report: the board, a board committee, or senior management outside IT operations. [2] It said a larger or more complex institution may add reporting lines into other independent functions, such as risk management. [2] Each choice carries a different trade-off, and the booklet left the choice to the institution. [2]
A line to the chief executive or another senior executive gives the CISO access to the person who sets budgets and priorities. Its weakness is that the same executive also answers for revenue and delivery. The booklet's warning against security decisions being unduly influenced by budgetary constraints applies here too. [2]
A line into a risk function places security alongside credit, market and operational risk. It fits the booklet's description of the CISO as an enterprise-wide risk manager. [2] Its weakness is distance from the systems: a risk function may lack the technical depth to weigh a dispute over a control.
A direct line to the board or a board committee gives the strongest independence. Its weakness is frequency. A board meets on a schedule, and day-to-day disputes need a faster route. In our reading, institutions that choose this design also need a day-to-day administrative line, and should document how the two lines divide decisions.
Whichever design an institution picks, the booklet's procedures look for the same evidence. [2] Examiners were to determine whether the structure gives the CISO appropriate authority and avoids conflicts of interest. [2] A written description of who decides what, and minutes that show the CISO's reports reaching the board, are the records that answer the question.
The segregation inside the security function
The booklet carried the same idea into the security function itself. [2] It said the institution should separate information security program management and monitoring from the daily security duties of IT operations. [2] It said the IT department should have personnel with daily responsibility for implementing the security policy. [2]
It added a further separation. [2] Responsibility for making changes and granting exceptions to policy should be segregated from the enforcement of the controls. [2] In our reading, this describes three roles: the people who run the controls, the people who decide exceptions, and the CISO who oversees and reports on both.
A small institution may not have three people for three roles. The separation still has to show in the records. An exception log that shows who approved each exception, separate from the operator who applied it, is evidence of the split. Its absence is evidence that one person both grants and enforces.
What the CISO was expected to do
The booklet listed responsibilities the CISO typically holds. [2] They included implementing the information security strategy approved by the board, and engaging with line-of-business management on new initiatives and their inherent security risks. [2] They included working with the lines of business to understand flows of information, monitoring emerging risks, and championing awareness and training. [2]
The list ended with reporting. [2] The CISO was to report significant security events to the board, the steering committee, government agencies and law enforcement, as appropriate. [2] The booklet also tied the CISO to the Interagency Guidelines Establishing Information Security Standards issued under the Gramm-Leach-Bliley Act. [2] It said the CISO is often responsible for implementing a program that satisfies them. [2]
The other roles around the CISO
The booklet described the chief information officer or chief technology officer as responsible for developing and implementing the IT strategy in line with the institution's risk appetite. [2] It said this position typically oversees the IT budget, performance management, acquisition oversight, professional development and training. [2]
It described business unit managers as holding IT responsibilities too. [2] Among them were documenting information flows in the business unit and notifying the CISO when business processes change. [2] They also included performing due diligence and ongoing monitoring of third-party providers. [2]
In our reading, the result is a map in which security risk is reported by one office, owned by several, and overseen by the board. The CISO's independence from IT operations is what keeps the reporting honest.
The board's list made oversight specific
The booklet's governance section opened with an action summary. [2] Boards of directors should oversee, and senior management should implement, a governance structure that includes effective IT governance, appropriate oversight of IT activities, comprehensive IT management and effective enterprise architecture. [2]
What the board should do
The booklet then listed what the board or a board committee should do. [2] The list is worth reading as a set of records, because each item implies a document an examiner can request.
- Review and approve an IT strategic plan aligned with the business strategy, including an information security strategy covering threats related to cybersecurity. [2]
- Oversee processes for approving third-party providers, including their financial condition, business resilience and IT security posture. [2]
- Oversee and receive updates on major IT projects, budgets, priorities and overall performance. [2]
- Oversee the adequacy and allocation of IT resources for funding and personnel. [2]
- Approve policies to escalate and report significant security incidents to the board, the steering committee, government agencies and law enforcement, as appropriate. [2]
- Hold management accountable for identifying, measuring and mitigating IT risks, and provide for independent, comprehensive and effective audit coverage of IT controls. [2]
The booklet said the board should approve the IT strategic plan, the information security program and other IT-related policies. [2] It said board members should understand IT activities and risks to carry out their responsibilities. [2]
Personnel as a board item
One item on that list is easy to pass over. The board should oversee the adequacy and allocation of IT resources for funding and personnel. [2] In our reading, this placed IT staffing on the board's agenda as an oversight matter, alongside the budget line management approves.
The booklet repeated the point in its section on human resources. [2] It said the board should actively and effectively oversee incentive compensation programs for IT management. [2] The aim was to ensure that those programs balance risk and reward and are compatible with effective controls and risk management. [2]
The steering committee as a record-keeper
The booklet allowed the board to delegate design, implementation and monitoring of specific IT activities to management or a committee, such as an IT steering committee. [2] It said the board remains responsible for overseeing IT activities and should provide a credible challenge to management. [2]
It set expectations for the committee's records. [2] The committee should have a charter that defines its responsibilities. [2] It should document meeting minutes and decisions and inform the board of its activities. [2] It should review and determine the adequacy of the institution's training, including cybersecurity training, for staff. [2]
The booklet said members need not be department heads but should understand IT policies, and each should have authority to make decisions for their business unit. [2] If the institution had a formal risk management function, risk staff should participate in an advisory capacity. [2]
For an examiner, the committee's minutes show whether challenge happened. A set of minutes that records only approvals is weaker evidence than one that records questions, deferrals and follow-up. The booklet's procedures asked examiners to determine whether the committee reported to the board on the status of IT activities in a way that let the board make decisions. [2]
What a board packet would carry
The booklet's list translates into a board packet with recognizable contents. In our reading, an institution following it would bring the board an IT strategic plan with its security strategy for approval. [2] It would bring periodic updates on major projects, budgets, priorities and performance. [2] It would bring a view of IT resources for funding and personnel, and the policy for escalating significant security incidents. [2]
It would also bring the results of independent audit coverage of IT controls. [2] The booklet said IT audit reports should go to appropriate management and directly to the board or a designated committee. [2] It said IT audit should be completely independent, with no role in designing or implementing controls. [2]
The packet is the board's record of oversight. An examiner reading it can tell whether the board approved what the booklet said it should approve, and whether it received what it should receive. Gaps in the packet are gaps in the evidence.
Management's annual work
The booklet assigned IT management a list of its own. [2] It included implementing effective processes for IT risk management, including those that relate to cybersecurity, and reviewing and annually approving those processes. [2] It included providing regular reports to the board on IT risks, strategies and changes. [2]
The list ended with a workforce item. [2] IT management should ensure that hiring and training practices are governed by appropriate policies to maintain competent and trained staff. [2] That item leads into the booklet's detailed workforce material.
The workforce file became part of the IT risk file
The booklet treated human resources as one of several functions that influence IT, alongside IT audit and compliance. [2] It said the HR function should hire and maintain competent and motivated IT staff. [2]
What a sound IT HR process included
The booklet listed components of an effective IT HR management process. [2] They were compensation planning, performance reviews, knowledge transfer mechanisms such as rotational assignments, training and mentoring. [2] It said IT management should integrate its management of HR with IT planning. [2]
The booklet said institutions should have programs to ensure staff have the expertise to do their jobs. [2] It said management should develop training programs for new technology and products before deployment. [2] It said an institution may need to look externally for expertise in specialized areas. [2]
Succession and backups
The booklet's succession language was specific. [2] It said the board and senior management should consider appropriate succession and transition strategies for key managers and staff members. [2] It named employment contracts, professional development plans and contingency plans for interim staffing of key management positions. [2]
It said management should have backup staff for key positions and should cross-train additional personnel. [2] It gave the objective as a smooth transition in the event of turnover in vital IT management or IT operations. [2]
The examination procedures turned this into checks. [2] Examiners were to identify key IT positions and review biographical data, such as résumés and training and development records. [2] They were to determine whether there were provisions for management succession, and whether backup personnel were identified and trained. [2]
Turnover as an examination topic
The procedures went further than succession. [2] They told examiners to review turnover rates of IT staff and discuss staffing and retention issues with IT management. [2] Alternatively, examiners could review turnover rates of IT management and discuss them with senior management. [2] They were to identify root causes of any staffing or expertise shortages, including compensation plans or other retention practices. [2]
The same objective told examiners to determine the institution's ability to attract and retain a competent workforce. [2] It asked whether job descriptions were reasonable and represented actual practice, whether employees had appropriate qualifications, and whether staffing levels were appropriate. [2]
In our reading, this part of the booklet widened what an IT leader needed to keep. Turnover data and an explanation of it are HR records. The booklet made them examination evidence about IT risk.
Hiring, access and agreements
The booklet's personnel section in its risk mitigation part covered screening. [2] It said institutions should mitigate risks posed by IT staff through appropriate background checks and screening of new staff. [2] It said the same controls are relevant for third-party provider staff, consultants and temporary personnel who support the IT function. [2]
It said management should document and confirm access privileges for each staff member based on the job description. [2] It said management should establish a timely process to review, update and remove access privileges when appropriate. [2] It said failure to remove access privileges, particularly for highly privileged individuals, represents significant risk. [2]
It said management should obtain signed confidentiality and nondisclosure agreements before granting new staff, contractors and temporary staff access to IT systems. [2] It said management should require periodic acknowledgment of acceptable use policies. [2]
The measures an examiner could ask for
The procedures did not name metrics for the workforce questions. [2] They did name the subjects: turnover rates, staffing levels, qualifications, succession, backups and training. [2] In our reading, a CIO preparing for an examination would keep a small set of measures that answer each subject directly.
- Turnover among IT staff and among IT management, by period, with the reasons recorded at exit.
- The count of key IT positions with a named and trained backup, against the total number of key positions.
- Open IT positions and how long each has been open.
- Completion of required training, including cybersecurity training, by role.
- Access reviews completed on schedule, and access removed promptly at departure, for privileged users.
The booklet sets no threshold for any of these numbers. [2] Their value lies in trend and explanation. In our view, a rising turnover figure with a written root-cause analysis and a response plan shows management at work, and the procedures asked examiners to identify root causes of staffing shortages. [2]
Contractors and temporary staff
The booklet extended its screening controls beyond employees. [2] It said the personnel controls are relevant for third-party provider staff, consultants and temporary personnel who support the IT function. [2] It said management should obtain signed confidentiality and nondisclosure agreements before contractors and temporary staff receive access. [2]
For an institution that relies on contract administrators or a managed service provider, this places the provider's staffing practices inside the institution's own personnel controls. In our reading, the contract should give the institution the right to confirm screening and to require prompt removal of access when a provider's staff member leaves the engagement.
Duties that cross departments
One procedure dealt with a familiar arrangement in smaller institutions. [2] If IT staff members have duties in other departments, examiners were to determine whether management is aware of the potential conflicts. [2] They were to check that conflicting duties are subject to appropriate supervision and compensating controls. [2]
For an institution where the network administrator also handles part of operations, this is the question an examiner would ask. The answer is a written description of the conflict and the control that offsets it.
What this asks of an HR department
The booklet's workforce material assumes an HR function that can produce IT-specific data. Turnover rates for IT staff, training records for key positions and current job descriptions are not always kept separately from the institution's general HR data. The procedures asked examiners to evaluate the adequacy of the HR function in this role. [2]
In our reading, the work falls on three people. The CIO or CTO identifies the key positions and their backups. HR keeps the turnover, training and qualification records by position. The board or a committee receives a periodic view of both, since the booklet put personnel adequacy on the board's list. [2]
The scale question was answered with alternatives, not exemptions
The booklet covered a wide range of institutions. [2] Its definition of "financial institution" ran from national banks to credit unions, and included technology service providers that serve them. [2] The guidance had to make sense for each.
Smaller institutions
The booklet did not exempt small institutions. It offered alternatives. [2] It said a smaller or less complex institution may have an information security officer perform the responsibilities of the CISO and report to senior management. [2] It said a larger or more complex institution may have additional reporting lines for the CISO into other independent functions, such as risk management. [2]
On steering committees, it said that in smaller or less complex institutions that may not have one, the functions would be performed by management, IT personnel, the board or a board committee. [2] On the CIO, it said that in less complex institutions, the IT manager may take on the responsibilities. [2]
The OCC's bulletin said the same in its note for community banks. [3] Community banks should implement effective IT governance and adopt IT risk management practices commensurate with the level of risk and complexity of their IT operations. [3]
A hypothetical small bank
Consider a hypothetical community bank with a four-person IT team and an outsourced core processor. Its IT manager acts as CIO. One team member carries the title of information security officer. The booklet's alternatives allow this structure. [2]
The security officer may report to senior management under the booklet's allowance for smaller institutions. [2] In our reading, the report should go to someone other than the IT manager, such as the chief executive or chief risk officer, so the line stays outside IT operations. [2]
The bank has no steering committee. Under the booklet, management, IT personnel, the board or a board committee would perform its functions. [2] In our reading, the bank should name which body does so and keep the same minutes a committee would keep.
The four-person team makes succession and backups a live issue. If the IT manager leaves, the booklet expects a plan for interim staffing and a trained backup. [2] For a team this size, the backup may be an outside firm under contract. The plan should say so, and the contract should allow the firm to step in on short notice.
The core processor sits within the booklet's definition of a technology service provider. [2] The bank's board oversees the process for approving it. [2] The bank's management monitors it. [2] Its staff and access controls fall within the bank's personnel controls to the extent its staff support the bank's IT function. [2]
What did not scale down
In our reading, some of the booklet's expectations did not change with size. The separation of program management and monitoring from daily IT operations applied to all. [2] The segregation of exception-granting from enforcement applied to all. [2] Succession provisions and backup personnel were checked for key positions regardless of size. [2]
In our reading, the hardest case is the institution with a single IT manager who also acts as security officer. The booklet's alternatives allow the security officer to report to senior management. [2] They do not relax the segregation of exception-granting from enforcement. [2] For that institution, a board-approved arrangement for outside review is one way to supply the separation that headcount cannot.
Credit unions and banks
The booklet's definition reached credit unions as well as banks. [2] It cited the information security standards each agency had issued under the Gramm-Leach-Bliley Act, including the National Credit Union Administration's appendix at 12 CFR 748. [2] The booklet's expectations for board oversight and independent audit coverage reach credit unions through that definition. [2]
Technology service providers
Service providers were within the booklet's definition. [2] For them, the workforce file is a client-facing matter as well as an examination matter. An institution's board was to oversee processes for approving third-party providers, including their IT security posture. [2] Business unit managers were to perform due diligence and ongoing monitoring of providers. [2]
In our reading, a provider's own CISO reporting line, succession planning and turnover data became questions its bank and credit union clients could reasonably ask. The booklet gave those clients the vocabulary to ask them.
The limits of guidance, and where rules went further
The booklet was examination guidance. [3] Neither the press release nor the OCC bulletin described it as a rule, and the OCC called it guidance. [1] [3] In our reading, its force lay in examination findings and the supervisory responses that follow them.
What it did not require
The booklet did not require a person with the title of CISO at every institution. [2] It allowed an information security officer in smaller institutions. [2] It did not set a number of IT staff, a turnover rate or a minimum of backups. [2] It asked examiners to judge appropriateness. [2]
It did not specify how often the CISO, as such, should report to the board. [2] It said the CISO should report significant security events, and that the steering committee should inform the board of its activities. [2] Its procedures did have examiners verify that the board was responsible for annually reviewing and approving a formal, written information security program, and for annually reviewing management's report on the status of compliance with the Information Security Standards. [2]
Where a state rule went further
New York's Department of Financial Services later adopted a regulation that addresses some of the same subjects for the entities it supervises. [5] Its cybersecurity regulation, 23 NYCRR Part 500, says it became effective March 1, 2017. [5] In its amended form, it requires each covered entity to designate a CISO. [5]
The amended Part 500 requires the CISO to report in writing at least annually to the senior governing body on the cybersecurity program. [5] It requires the senior governing body to exercise oversight, including by confirming that management has allocated sufficient resources to an effective program. [5] It allows the CISO to be employed by an affiliate or third-party service provider, with conditions. [5]
The New York rule applies to entities licensed or regulated by the Department, not to every institution the FFIEC booklet reached. Organizations should check with counsel on whether it applies to them. In our reading, the rule's reporting and resource language echoes the booklet's board-oversight items, but turns them into requirements, including a written report from the CISO at least annually.
The strongest case against our argument
A fair objection is that boards and CISOs were already organized this way at larger banks before November 2015, and that the booklet described existing practice. We have no source that measures how institutions were organized at the time, and we make no claim about it. Our argument is about examination: the booklet put the reporting line and workforce data into the procedures examiners used. [2]
A second objection is that guidance without a rule is weak. The booklet's procedures answer this in part. An examiner who finds that the CISO reports to IT operations, or that no backup exists for a key administrator, has a documented basis in the Handbook for the finding. [2] In our reading, the strength of such guidance lies in the examination record it produces.
What the booklet cost to follow
The booklet's expectations carry real costs, and an honest reading should name them. Moving a CISO's reporting line can mean a new executive relationship and a change in how security funding is approved. Naming and training backups for key positions takes time from people who are already scarce. Keeping IT-specific turnover and training data may require changes to HR systems that were built for the whole institution.
The booklet acknowledged trade-offs in its own terms. [2] It said cost and benefit decisions will always need to be made. [2] It said the institution's size and complexity play a role in the reporting structure. [2] What it asked was that security decisions not be unduly influenced by operational ease or budget, and that the structure show the CISO's authority. [2]
In our reading, the cheapest compliance is documentary. An institution that cannot yet change its structure can still write down the reporting line, the conflicts it creates and the controls that offset them. That record gives an examiner something to evaluate, and gives the board a basis to decide whether the structure should change.
How it fit with the rest of the Handbook
The Management booklet did not stand alone. [2] Its information security section referred readers to the Handbook's Information Security booklet for more detail. [2] Its IT audit section referred to the Audit booklet. [2] The press release said the revision brought management-related concepts from other booklets into this one. [1]
That consolidation matters for planning. An institution preparing for an IT examination would expect the Management booklet's governance and workforce questions to frame the review, with the subject booklets supplying detail. [1] [2] In our reading, the workforce file belongs at the front of that preparation, since it answers questions the other booklets assume have been settled.
What we would tell a bank or credit union today
Three records answer the core of the booklet's workforce questions. The first is an organization chart that shows the CISO or security officer's reporting line and its independence from IT operations. The second is a key-position list with named backups, their cross-training and a succession plan. The third is IT turnover data with a written explanation of causes and responses.
Each of these is cheap to keep and expensive to reconstruct before an examination. The booklet told examiners to ask for them. [2] An institution that keeps them current can show its management of IT rather than describe it.
With hindsight
A Management booklet with the 2015 booklet's structure was still part of the IT Handbook in 2026. [6] An Internet Archive capture of the FFIEC's IT Handbook InfoBase page for the booklet, taken August 16, 2026, describes the Management booklet as one of several that comprise the IT Handbook. [6]
That capture lists the same section structure the 2015 booklet carried. [2] [6] It runs from governance, IT governance and board of directors oversight, through IT management and enterprise architecture, to IT responsibilities and functions, and then to risk management. [6]
The FFIEC's other 2015 cybersecurity product had a different fate. On August 29, 2024, the OCC issued Bulletin 2024-25, the FFIEC's statement that it would sunset the Cybersecurity Assessment Tool on August 31, 2025. [4] The bulletin said the tool had been released in June 2015 as a voluntary assessment tool. [4]
The bulletin said the FFIEC had decided not to update the tool to reflect new government resources. [4] It named the National Institute of Standards and Technology's Cybersecurity Framework 2.0 and the Cybersecurity and Infrastructure Security Agency's Cybersecurity Performance Goals. [4] It said supervised institutions could refer directly to those resources. [4]
A footnote said the National Credit Union Administration would continue to support its Automated Cybersecurity Examination Tool, which was derived from the FFIEC tool. [4] In our reading, the self-assessment tool was retired while the governance booklet stayed in the Handbook. The bulletin gave reasons only for retiring the tool.
New York's cybersecurity regulation turned the CISO into a required role for the entities the Department supervises. [5] Part 500 states that it became effective March 1, 2017. [5] In its amended form, it requires a designated CISO who reports in writing at least annually to the senior governing body. [5] It requires that body to have sufficient understanding of cybersecurity matters to exercise oversight, which may include the use of advisors. [5]
The amended Part 500 defines the senior governing body as the board of directors, an appropriate committee, or an equivalent body. [5] Where none exists, it is the senior officer or officers responsible for the cybersecurity program. [5] In our reading, that definition plays the same role as the booklet's allowance for smaller institutions without steering committees. [2] [5]
What held up from the week of November 10, 2015 was the booklet's view of the CISO as an enterprise risk role, separate from IT operations, reporting to the board or senior management. [2] A Management booklet with the same contents list was still in the Handbook in the August 2026 capture, which does not give the booklet's date. [6] New York's rule requires the role and its board reporting for the entities it covers. [5]
The amended Part 500 also addresses the outsourced CISO. [5] It allows the CISO to be employed by an affiliate or a third-party service provider. [5] In that case, the covered entity keeps responsibility for compliance and designates a senior member of its own staff to oversee the provider. [5] It must also require the provider to maintain a cybersecurity program that protects the entity. [5] That echoes the booklet's view that a function can be delegated while accountability stays with the institution. [2]
What did not change was the booklet's reliance on judgment. [2] It set no staffing levels or turnover thresholds, and the materials we opened show no later FFIEC product that did. [2] [4] [6] Workforce questions remain for examiners and boards to judge case by case.
Spotted an error? Tell us and we will check it and correct the article where needed.