Before signing your NYDFS Part 500 certification, New York financial firms should review these cybersecurity controls, policies, access, vendors, and risks.

NYDFS Part 500 certification readiness graphic with shield and laptop

Signing the annual NYDFS Part 500 certification takes about thirty seconds. What should take considerably longer is everything that happens before you sign it.

I've talked to executives at covered entities across New York who treat this certification the way most people treat a software license agreement. You scroll, you attest, you move on. But the certification isn't asking you to confirm that you've read the terms. It's asking you to confirm that your organization has actually built and maintained a functioning cybersecurity program that meets specific regulatory requirements.

That's a different thing entirely.

The Department of Financial Services designed Part 500 with real intention. It's not a checklist you complete once and file away. It's a living framework that expects your cybersecurity posture to evolve alongside your business, your vendors, and the threats your industry faces. The certification process is supposed to force that ongoing review. But only if you actually do the review.

What follows is a walk through the areas that most consistently reveal gaps when we help financial firms prepare for this process.

Your Cybersecurity Program: What the Regulation Actually Expects

Part 500 requires covered entities to maintain a cybersecurity program based on a risk assessment. That sounds straightforward, but the phrase 'based on a risk assessment' is doing a lot of work.

Has your risk assessment been updated recently?

A risk assessment completed two or three years ago isn't meeting this requirement. Your environment has changed. You may have added cloud services, onboarded new vendors, shifted to remote or hybrid work, or expanded your team. Each of those changes introduces new risks that the original assessment may not have captured.

The risk assessment isn't just a document. It's supposed to inform your entire cybersecurity program, including your policies, your controls, and your incident response planning. If the assessment is stale, the program it's supporting is stale too.

Does your written policy actually reflect what you do?

Most organizations have a cybersecurity policy. Fewer have one that accurately describes what they actually do. Part 500 requires a written policy covering a fairly specific list of areas, including data governance, access controls, system and network monitoring, application security, and incident response, among others.

Pull the policy out and read it honestly. If someone handed it to a regulator and they started asking questions based on what it says, would your answers match? If there's a gap between the policy and reality, that's the problem to address. And it's better to find it yourself.

Access Controls and Privileged Accounts

This is one of the areas where we consistently find the most exposure. Not because organizations are careless, but because access tends to accumulate quietly over time.

Who actually has access to what

Part 500 requires multi-factor authentication for individuals accessing internal networks from an external network, as well as controls over access to nonpublic information and privileged accounts. If you haven't done a formal access review recently, there's a reasonable chance some accounts have more access than they should.

Former employees. Vendors who completed a project months ago. Internal staff whose roles changed but whose permissions didn't. These situations are extremely common, and they're exactly what regulators look for.

Privileged account oversight

Part 500 gives specific attention to privileged accounts, meaning accounts with administrative or elevated permissions. These represent higher risk if compromised, so the regulation expects more oversight around them. That includes limiting who has them, monitoring how they're used, and reviewing them on a regular basis.

If your IT team hasn't audited privileged accounts as part of your certification preparation, that review belongs on the list.

Third-Party and Vendor Risk

Third-party risk is one of the most significant areas of focus in the amended Part 500 requirements. Financial firms are required to assess the cybersecurity practices of their critical vendors and include relevant contractual protections in vendor agreements.

What 'critical vendor' actually means in practice

It doesn't mean every vendor. It means the ones whose compromise or failure could expose nonpublic information or disrupt your operations. Your core banking platform. Your document management vendor. Your payroll processor. Your IT provider. Those are the ones that warrant formal assessment.

Here's what we see most often: firms with strong internal controls that haven't applied the same scrutiny to vendors who have equally deep access to their systems and data. A vendor with administrative access to your environment who doesn't use MFA is your problem too, regardless of what their contract says.

Contracts and ongoing monitoring

Vendor contracts should include representations around cybersecurity practices, notification requirements in the event of a breach, and, where applicable, the right to audit. Those provisions need to actually be in the agreements, not just understood informally.

Beyond the contract, you need a process for monitoring vendors on an ongoing basis. Annual review at minimum. More frequently if the vendor handles sensitive data or has privileged access to your environment.

Incident Response Planning and Testing

Part 500 requires a written incident response plan. And it's worth being specific about what that means, because a plan that exists only as a document in a shared drive isn't really a plan. It's a file.

Does anyone actually know what to do?

An incident response plan should describe roles, responsibilities, communication protocols, and escalation paths clearly enough that someone could follow it during a stressful event. That means identifying who declares an incident, who handles communications internally and externally, who contacts regulators if required, and who manages the technical response.

The regulation has specific requirements around when and how covered entities must report cybersecurity events to DFS. Those timelines are tight, and they're not the kind of thing you want to be figuring out for the first time during an actual incident.

Testing: not optional

Part 500 requires that incident response plans be tested. Annual tabletop exercises are the most common approach, and they're genuinely useful when done well. The goal isn't to confirm that the plan works perfectly. The goal is to find the gaps before someone else does.

If your last tabletop exercise was more than a year ago, or if you've never done one, that's a material gap worth addressing before your next certification.

Data Classification, Encryption, and Retention

One question that comes up regularly when we're helping organizations prepare: do you actually know where your nonpublic information lives?

Part 500's protections are tied to nonpublic information, meaning customer records, financial data, anything that could be used to identify or harm someone if exposed. If you don't have a clear picture of where that data is stored, who can access it, and how it's being protected, it's genuinely difficult to certify that you're protecting it adequately.

Encryption requirements

Part 500 requires encryption of nonpublic information both in transit and at rest, with limited exceptions. That sounds simple, but in practice data often ends up in places organizations don't expect. Email threads. Shared drives. Backup systems. Portable devices. Vendor platforms.

A data mapping exercise, even an informal one, can surface a lot of situations that weren't on anyone's radar.

Retention and disposal

You also need documented policies around how long data is retained and how it's disposed of when it's no longer needed. Keeping data longer than necessary increases your exposure. This is an area where we find a lot of organizations have policies that are technically in place but haven't been reviewed in years.

What to Do With What You Find

Here's the honest answer: most organizations doing a thorough pre-certification review will find something. That's not a sign of failure. It's a sign that the review is working.

The right approach isn't to ignore gaps in order to sign the certification. It's to document what you've found, put a remediation plan in place, and ensure your certification accurately reflects your current state. If there are areas where your program is still maturing, some provisions allow for risk-based compensating controls. That's worth understanding before you sign.

The firms that navigate this process well aren't the ones with perfect programs. They're the ones that take the process seriously, know their environment, and have someone helping them connect regulatory language to operational reality.

How TAG Solutions Supports Financial Firms Through Part 500

TAG Solutions has worked with organizations across New York's Capital Region for more than 30 years. The Part 500 certification conversation comes up with nearly every financial firm we work with, and it almost always surfaces the same gap: leadership has attested to compliance, while the actual program hasn't been systematically reviewed against what the regulation requires.

Every TAG client gets an assigned vCIO. In the context of Part 500, that means having someone who stays current on what DFS expects, who can translate regulatory language into practical priorities, and who helps your leadership make informed decisions about where your actual exposure is. Not someone who hands you a checklist and bills by the hour.

We work with financial firms to build cybersecurity programs that support genuine certification confidence, not just regulatory paperwork. The difference matters when an examiner asks questions.

We back our work with service guarantees.

________________________________________________________________________

If your organization's certification window is approaching and you haven't done a systematic review yet, that's the right time to have a conversation.

Your assigned vCIO will work directly with your leadership team to assess your current program against Part 500 requirements, identify gaps, and build a prioritized remediation plan that holds up to regulatory scrutiny.

________________________________________________________________________

Questions Financial Executives Ask Most Often About Part 500

We have an IT team and a cybersecurity vendor. Doesn't that mean we're covered?

Not necessarily. Part 500 doesn't ask whether you have security vendors. It asks whether you have a functioning cybersecurity program that meets specific requirements, based on a current risk assessment, with documented policies and tested controls. Having the right vendors is part of the answer. Having evidence that the program is actually operating as described is the rest of it.

If we find gaps during our pre-certification review, does that mean we can't certify?

No, and here's the point most executives miss. The certification is not asking you to confirm perfection. It's asking you to confirm that a functioning program exists. If you've identified gaps and have a documented remediation plan in place, that's part of responsible program management. What you can't do is certify controls that aren't actually in place. Document what you find, address it systematically, and be honest about where you are.

Our vendor says they're SOC 2 compliant. Does that satisfy our third-party risk requirements under Part 500?

Different standards entirely. A SOC 2 report tells you something useful about a vendor's controls at a point in time. Part 500 doesn't ask whether your vendor passed an audit. It asks whether you've assessed their cybersecurity practices, included appropriate contractual protections, and are monitoring them on an ongoing basis. Those are different things, and a SOC 2 report doesn't complete that picture on its own.

How frequently do we need to update our risk assessment?

At minimum annually, and whenever there are significant changes to your business or technology environment. New systems, major vendor transitions, acquisitions, meaningful shifts in how your team works. Any of those should trigger a fresh look. Waiting for the annual cycle when your environment has materially changed is one of the more common ways organizations end up with a compliance program that's technically in place but practically out of date.

What's the gap we most often find when helping firms prepare for certification?

Access controls, almost every time. Specifically, privileged account management and MFA gaps for users accessing internal systems from outside the network. These aren't exotic failures. They're operational situations that drift quietly over time: accounts that weren't revoked, vendors whose access was never reviewed, admin credentials that got shared for convenience. All fixable. But they need to be found first.