On 10 September 2026, the New York State Department of Financial Services (NYDFS) published guidance on cyber risk assessments. It is addressed to the organisations it regulates under its Cybersecurity Regulation, 23 NYCRR Part 500. The guidance says it “does not create new obligations”. Instead, it explains what NYDFS expects, based on gaps it has seen in examinations and investigations.
Most organisations don’t answer to NYDFS. But the guidance is one of the clearest descriptions from a regulator of what a risk assessment should be. It is worth reading wherever you are.
What’s changing
The guidance is titled “Guidance on How to Conduct and Use Risk Assessments Required by the DFS Cybersecurity Regulation”. It names five common gaps. Asset scope is incomplete, or methods are weak or inconsistent. Evolving or interconnected risks are missed. Governance and risk treatment are weak. And assessments don’t shape the security programme.
It then covers five areas.
Governance and oversight. A Senior Officer or the Senior Governing Body approves the written risk assessment policies at least once a year. A CISO or Senior Officer oversees the process, with input from the business, operations, compliance and legal. The CISO reports material cyber risks to the senior governing body.
A repeatable method. Use consistent likelihood and impact criteria, so results can be compared over time. Draw on threat intelligence, incident trends, vulnerability scans, penetration tests and audit findings. NYDFS doesn’t require a particular method. It mentions NIST CSF 2.0, the Cyber Risk Institute Profile v2.2 and ISO 27005:2022.
Scope. Build the assessment on a current asset inventory. Include emerging risks such as artificial intelligence and software supply chain attacks. Weigh suppliers by how critical their service is, how sensitive the data is and how connected they are. Look for concentration risk, where many critical functions rely on the same platform or provider.
Documentation and traceability. Record how each risk was identified, assessed and treated, and why. Link each risk to the controls that reduce it. Document risk acceptance decisions with a justification. The guidance recommends “a risk register or similar tracking tool”.
Integration and updates. The assessment should drive policies, controls and testing plans, not sit apart from them. Review it at least once a year, and whenever a change materially affects cyber risk. Examples include major system migrations, mergers, significant outsourcing and a critical vulnerability being actively exploited.
What it means for you
If NYDFS regulates you, these requirements already apply. The guidance has no separate deadline, but Sheppard Mullin suggests checking that your assessment reflects your current systems, suppliers and processes. You should also be able to show how risks shaped your controls and acceptance decisions.
If NYDFS doesn’t regulate you, the guidance still works as a checklist. Ask yourself:
- Is your asset inventory complete, and does it drive your assessment?
- Do you score risks the same way each time?
- Can you trace each risk to its controls, and each acceptance to a reason?
- Do you reassess when something material changes, not only once a year?
How RiskWitness helps
RiskWitness holds the record this guidance describes. This is how the five areas look in the app.
Start from your assets. Record your assets with owners, where they are kept or hosted, and the risks, controls and suppliers linked to them.
Score risks consistently. Each risk has an owner, and likelihood and impact before and after controls. Every risk is scored on the same scales, so you can compare results over time.
Link risks to controls, and test them. Link each risk to the controls that reduce it, with how effective each one is. Record control tests and their results.
Weigh your suppliers. Rate each supplier’s criticality. Send questionnaires, keep their assurance evidence and record your reviews. Link suppliers to the assets and risks they affect.
Record every decision. Each risk has a treatment decision: reduce, transfer, avoid or accept. Acceptances carry a reason and an expiry. Outside tolerance, a named approver signs them off.
Act on what you find. Turn gaps into actions with owners and due dates. Set review dates on risks, and revisit them when something material changes.
Report to the people who oversee it. Record committee meetings, minutes and decisions. Give the board a PDF report or slide deck.
Every change is kept in a history that shows who did what, when, and the old and new values. Nobody can edit or delete it. The board, an auditor, a customer or a regulator may ask how a risk was assessed, and why it was accepted. The answer is already written down.
Sources
- Guidance on how to conduct and use risk assessments required by the DFS Cybersecurity Regulation, New York State Department of Financial Services, 10 September 2026
- NYDFS issues guidance on cybersecurity risk assessments, Sheppard Mullin, 15 October 2026
- NYDFS issues guidance on risk assessments, WilmerHale, 22 October 2026
