Blog Viewer

How Law Firms Can Navigate Growing Client and Regulator Demands

By Kevin Foster posted 10 days ago

  
For those of us working in cybersecurity and compliance at law firms, there has been a noticeable shift over the last several years. Security is no longer something that happens primarily behind the scenes.
 
Our clients want to know what we are doing to protect their information. Regulators are paying attention. Attorneys and firm leadership need answers. And the security and compliance teams are often right in the middle of all of it.
 
That is not necessarily a bad thing. Greater attention to security has helped make law firms stronger. But it has also created a challenge: how do we keep up with increasing client and regulatory demands without turning compliance into an endless exercise of answering questionnaires and collecting evidence? Many of us know this all too well.
 
There is no simple answer, but I think it starts with changing how we look at compliance.

The Client Security Questionnaire Isn't the Finish Line
 
Anyone who has worked in law firm security for a while is familiar with the client security questionnaire. For me, it’s one of my primary responsibilities.

Some are relatively straightforward. Others can turn into lengthy exercises involving cybersecurity, privacy, business continuity, incident response, vendor management, data retention, access controls, artificial intelligence, and just about every other part of the firm's technology environment.
 
It can be tempting to approach these assessments as individual projects: receive the questionnaire, find the answers, submit it, and move on to the next one.
 
The problem is that the next one is coming.

Instead, firms can use these requests as an opportunity to look for common requirements and build a repeatable process around them. If clients routinely ask for the same policies, controls, testing results, or supporting documentation, that tells us something about what our security program needs to be able to demonstrate.

That changes the exercise from How do I answer this questionnaire? to How do I make sure we are prepared to answer these questions consistently?

That is a more sustainable approach.

Compliance and Security Have to Tell the Same Story
 
One of the most important things firms can do is make sure that what they say about their security program matches what is actually happening in the environment.
 
That sounds obvious, but it gets harder as the number of client assessments grows.
 
The security questionnaire may ask whether the firm has an incident response plan, performs security awareness training, evaluates vendors, reviews access, maintains cybersecurity policies, or tests its controls.
 
Checking "yes" should not end the conversation.

If we say we have a process, we should know who owns it, when it was last reviewed, how it works, and what evidence we can produce to support that answer.
 
This is where cybersecurity operations and compliance become closely connected. Policies describe what we expect to happen. Processes turn those expectations into something repeatable. Technical controls help enforce them. Documentation and evidence allow us to demonstrate that those things are actually taking place.
 
The goal is not simply to have the right answer. The goal is to have an answer we can stand behind.

Clients Are Part of the Security Conversation Now
 
Another change is that clients are becoming much more involved in how firms protect and handle their information.

From a cybersecurity perspective, that matters.
 
Client requirements can affect how data is stored, who can access it, which technologies can be used, and what the firm may be required to do when something goes wrong.
 
Those obligations cannot live only with the person completing the questionnaire.

The right people need to be involved when requirements affect technical controls, legal obligations, privacy, records management, vendors, or business processes. Security may own part of the response, but it rarely owns all of it.
 Just as importantly, those requirements need to make their way back into operations. There is little value in agreeing to a security requirement during an assessment if the people responsible for the underlying technology or process never know about it.

Compliance works best when it connects the promise to the practice.

Regulation Adds Another Layer
 
Client demands are only one part of the picture. Law firms also operate in an environment where regulatory expectations regarding cybersecurity and data protection continue to matter.
 
This creates an interesting dynamic.

A firm may be responding to client expectations, regulatory obligations, contractual requirements, industry standards, cyber-insurance requirements, and its own internal security standards at the same time.
 
Treating each requirement as an entirely separate compliance project can quickly become difficult to manage.
 
A better approach is to work from the firm's core security controls.
 
Instead of asking, "What do we need to do for this particular questionnaire?" start with, "What control do we have in place, what risk does it address, and what evidence demonstrates that the control is working?"
 
That foundation can then support multiple compliance needs.
 
Exceptions and client-specific requirements will always exist. But having a strong baseline makes those exceptions much easier to identify and manage.

The Evidence Matters
 
One lesson I have learned from working with assessments is that having a policy and being able to demonstrate compliance with that policy are two different things.

A mature compliance process should make evidence part of normal operations rather than something everyone has to scramble to find when an assessment arrives.
 
If a firm conducts security awareness training, for example, there should be records supporting it. If an incident response plan is tested, the firm should be able to document the exercise and the lessons learned. If vendors are assessed, there should be a defined process and a record of that assessment.

This is not about generating paperwork for the sake of paperwork.
 
It is about being able to demonstrate that the security program described on paper is the same security program operating in practice.
 
And when that evidence is organized and accessible, responding to clients becomes much easier.

Don't Let Compliance Become a Checkbox Exercise…Please
 
There is also a danger in becoming too focused on passing assessments.
 
A firm can have excellent questionnaire responses and still have security problems.

Cybersecurity ultimately comes back to managing risk. Compliance can help identify where controls should exist and provide a structure for demonstrating that they do, but checking a box does not eliminate the underlying risk.
 
This is why security and compliance teams need to keep asking practical questions:

     • Is this control actually reducing risk?
     • Is it working the way we say it is?
     • Can we prove that?
     • Does the person responsible for the control understand their responsibility?
     • Are client-specific requirements making their way to the teams that need to implement them?
     • Are we fixing gaps when assessments uncover them?

Those questions move the conversation beyond mere compliance.

Turning the Pressure Into an Advantage
 
Client and regulatory scrutiny are not going away.

If anything, firms should expect questions about cybersecurity, privacy, third-party risk, artificial intelligence, incident response, and other emerging areas to continue evolving.
 
But that pressure can also be useful.

Every assessment gives us information about what clients care about. Every regulatory change gives us an opportunity to revisit our controls. Every difficult question can expose an area where our documentation, processes, or security program could be stronger.
 
The firms that handle this well will not necessarily be the ones with the largest security teams or the most complicated compliance programs.
 
Ultimately, the goal should not be to become better at answering questionnaires.
 
The goal should be to build a security program that makes the questionnaires easier to answer.
 
That distinction may sound small, but when client and regulatory demands keep coming, it makes a very big difference.

Key Takeaways




#Security
#200Level
#InformationGovernanceorCompliance
#Cybersecurity
#SecurityProfessionals

0 comments
231 views

Permalink