SOX Section 404
Build management’s internal-control assessment and support an integrated external audit where required.
New York Department of Financial Services Cybersecurity Regulation, 23 NYCRR Part 500
Map DFS licensing to cybersecurity obligations, annual filings and incident escalation.
Persons operating under a covered DFS license, registration, charter, certificate, permit, accreditation or similar authorization. Some exemptions and Class A requirements apply.
A risk-based cybersecurity program, evidence for required designations and filings, and an incident reporting workflow.
Verify partial exemptions requirement by requirement. Identify Class A status instead of assuming it from the company’s parent or industry.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
NYDFS Part 500 kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Map regulated entities and exemptions · Counsel + compliance [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
A licensed firm receives a ransomware alert from a service provider. The incident lead records when the firm determines the event meets DFS reporting criteria, checks the separate extortion-payment rules if relevant, and saves the portal confirmations.
Check whether another entity in the group has separate FTC Safeguards Rule duties.
Compare the EU financial resilience program if you also operate there.
Use section 500.17 to determine the required certification or acknowledgment and authorized signers.
Official reference (opens in a new tab)Report as promptly as possible. Extortion payments have separate notice and explanation clocks.
Official reference (opens in a new tab)Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Map regulated entities and exemptions | Counsel + compliance | Before configuring the program and filing | Set a start date | Applicability matrix; Accountability map | Open |
| Build controls and track evidence | CISO + control owners | Ongoing | Set a start date | Control matrix; Internal audit report; Management review minutes | Open |
| Practice notification and extortion workflows | Incident lead + legal | On incident and during drills | Set a start date | Incident classification; Reporting templates; Exercise record | Open |
| Prepare the annual filing | Compliance + authorized signers | By applicable annual deadline | Set a start date | Evidence index; Management assertion; Submission package | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify licenses, applicable provisions, exemptions and Class A triggers. Assign the senior governing body, CISO and operational owners as required.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Maintain risk assessment, policies, detection, access and recovery under the provisions that apply. Test safeguards and retain evidence of leadership oversight.
Fictional details. Use the same fields with evidence from your work.
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Fictional details. Use the same fields with evidence from your work.
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.
Record the event, determine regulatory reporting status and track all clocks. Include service-provider escalation and separate payment documentation when applicable.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
Fictional details. Use the same fields with evidence from your work.
Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.
Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.
Fictional details. Use the same fields with evidence from your work.
An absent participant can see what was tested, what happened and why an action was assigned.
Send approved findings to action owners and file the record for governance or assessment.
Gather prior-year evidence. Evaluate material compliance, use the applicable certification or acknowledgment process, and retain documentation and the receipt.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Fictional details. Use the same fields with evidence from your work.
The signer can explain the basis for each statement and the record reflects the required scope and period.
Give the executed document to the relevant recipient under the engagement or regulation. Use the worksheet to organize review.
Fictional details. Use the same fields with evidence from your work.
The submitted package can be recreated from the index and the receipt is linked to the exact files.
Send the approved package through the official channel. Treat the download as an index, and use issuer forms where required.