Most law firms have never formally evaluated their IT provider against ABA confidentiality standards.
Not because managing partners don’t care about compliance. Not because the obligation isn’t clearly established. But because the conversation about technology and professional responsibility has historically stayed at the level of general awareness — “we should probably look at that” — without ever becoming a structured, documented review.
That gap is exactly where professional liability exposure quietly accumulates.
ABA Model Rule 1.6(c) requires attorneys to make reasonable efforts to prevent unauthorized access to client information. ABA Formal Opinion 477R extends that obligation to the vendors and technology platforms your firm uses every day. When your IT provider has access to client files, email communications, matter management systems, or any infrastructure that touches protected client data — they are operating within the scope of your professional responsibility obligations, whether they know it or not.
Has your IT provider ever been formally evaluated against those standards? If not, this framework is where that evaluation begins.
Why Formal Vendor Evaluation Is a Professional Responsibility Issue
Many firms treat IT vendor selection as an operational decision — compare pricing, check references, sign a contract. The ABA’s guidance makes clear that it is also a compliance decision, and one that carries ongoing obligations beyond the initial selection.
ABA Formal Opinion 477R establishes that attorneys must exercise reasonable care in selecting technology vendors and must consider the sensitivity of client information when evaluating how it is transmitted, stored, and accessed. The opinion does not create a safe harbor for delegating those decisions to someone else. The attorney — and the firm — remains responsible for the outcome.
ABA Formal Opinion 483 adds that when a security incident occurs involving client data, the firm’s obligations include detecting the breach, stopping the intrusion, assessing what was compromised, and notifying affected clients. A firm that has never formally evaluated its IT provider’s incident response capability is poorly positioned to meet any of those obligations quickly.
The result is that vendor evaluation is not a one-time procurement activity. It is a recurring professional responsibility practice.
What a Formal Evaluation Actually Looks Like
A structured IT vendor evaluation against ABA standards covers six core areas. Each one maps directly to specific obligations under the Model Rules and the ABA’s formal opinions.
1. Confidentiality Agreements and Contractual Protections
The starting point of any compliant vendor relationship is a written agreement that specifically addresses client confidentiality obligations.
What to verify:
- Does your firm have a written agreement with your IT provider that addresses confidentiality of client information?
- Does the agreement prohibit the vendor from using or disclosing client data for any purpose other than providing services to your firm?
- Does the agreement require the vendor to implement and maintain reasonable security safeguards?
- Does the agreement require the vendor to notify your firm promptly if a security incident occurs?
- Does the agreement specify how client data is handled upon contract termination — including secure deletion or return?
Many firms have standard IT service agreements that address service levels and pricing but say nothing specific about client confidentiality, data handling, or breach notification. Under ABA Formal Opinion 477R, that gap is a compliance problem regardless of how long the relationship has existed.
Red flags: Vendor refuses to include confidentiality provisions. Agreement is entirely silent on client data. No breach notification requirement exists. Data handling at termination is unaddressed.
2. Data Security Controls
ABA Model Rule 1.6(c) requires reasonable efforts to prevent unauthorized access. What constitutes reasonable effort depends on the sensitivity of the matters the firm handles — but there is a functional baseline that applies across practice areas.
What to verify:
- Does the vendor encrypt client data both at rest and in transit using current standards?
- Does the vendor require unique credentials and multi-factor authentication for access to firm systems?
- Does the vendor maintain audit logs documenting who accessed what data and when?
- Does the vendor conduct regular vulnerability assessments or penetration testing?
- Does the vendor have documented security policies that apply to all employees with access to firm data?
- Does the vendor carry cyber liability insurance with coverage adequate for the scope of their engagement?
The ABA’s guidance does not require attorneys to become technical security experts. It does require them to ask these questions — and to get specific, documented answers rather than general assurances.
Red flags: Vendor cannot describe encryption standards specifically. No MFA requirement. Audit logging is disabled or unavailable. No third-party security assessment on record. Cyber insurance is absent or inadequate.
3. Subcontractor and Third-Party Oversight
Your IT provider almost certainly uses subcontractors — cloud storage platforms, backup vendors, remote access tools, monitoring services. Each one that handles or can access client data extends the confidentiality obligation.
What to verify:
- Does your IT provider maintain a documented list of subcontractors with access to firm data?
- Does your firm have written agreements with those subcontractors, or has the primary vendor obtained equivalent protections on your behalf?
- Is your firm notified when subcontractors change?
- Has the vendor assessed the security practices of its key subcontractors?
This is one of the most consistently overlooked areas in law firm vendor evaluation. A firm may have a solid written agreement with its primary IT provider while having no visibility into the cloud platforms, backup systems, or third-party tools that provider relies on to deliver services.
Red flags: Vendor cannot identify its subcontractors. No written agreements covering subcontractor data handling. Vendor changes subcontractors without notification. No assessment of subcontractor security practices.
4. Incident Response and Breach Notification Capability
ABA Formal Opinion 483 establishes that attorneys have obligations both during and after a security incident — including notifying affected clients when their information has been compromised. A firm cannot meet those obligations if its IT provider lacks the capability to detect, contain, and report a breach in a timely and organized way.
What to verify:
- Does the vendor have a documented incident response plan?
- What is the vendor’s committed notification timeline when a security incident is detected?
- Has the incident response plan been tested within the past 12 months?
- Does the vendor preserve forensic evidence during an incident investigation?
- Does the vendor provide written incident reports documenting what occurred, what data was affected, and what corrective actions were taken?
The combination of Rule 1.6 and Rule 1.4 (duty of communication) creates an affirmative obligation to notify clients when their data is compromised. That obligation begins with the firm being promptly informed by its vendor — which requires the vendor to have a functioning, practiced response capability.
Red flags: No documented incident response plan. Notification timeline is vague or undefined. Plan has never been tested. No forensic preservation process. No written incident reporting.
5. Access Controls and Personnel Security
Client data should be accessible only to the people who need it to perform specific services for your firm. Vendors that maintain broad, unmonitored access to firm systems create unnecessary confidentiality exposure.
What to verify:
- Does the vendor limit employee access to client data based on role and specific service needs?
- Are access privileges reviewed regularly and revoked promptly when employees leave?
- Does the vendor conduct background screening for employees with access to firm data?
- Does the vendor require its employees to sign confidentiality agreements?
- Are privileged access activities — system administration, remote access — logged and monitored?
Personnel security is where many firms have the least visibility into their vendor’s practices. Yet it represents one of the most direct pathways to unauthorized client data exposure.
Red flags: No role-based access limitation. Terminated employee access not promptly revoked. No employee confidentiality agreements. No background screening for employees with data access.
6. Documentation and Ongoing Compliance Evidence
A vendor that is genuinely operating to a compliance standard should be able to produce documentation supporting that claim. The ability to produce this documentation is also what allows your firm to demonstrate reasonable efforts if your compliance is ever questioned.
What to verify:
- Can the vendor provide written security policies covering the areas above?
- Can the vendor provide results of third-party security audits or certifications (SOC 2 Type II, for example)?
- Does the vendor maintain records of employee security training completion?
- Can the vendor provide its cyber insurance declarations page?
- Is the vendor willing to respond to a formal vendor assessment questionnaire?
A vendor that resists documentation requests is a vendor that makes it impossible for your firm to demonstrate compliance. Under the ABA’s framework, that resistance is itself a compliance problem.
Red flags: Vendor cannot produce security policies. No third-party audit on record. Training records unavailable. Cyber insurance cannot be verified. Vendor declines to complete a formal assessment.
What the Results Usually Reveal
Firms that go through this evaluation for the first time typically find one of three situations.
The vendor is broadly compliant but undocumented. The security controls exist, but nothing is written down in a way that allows the firm to demonstrate reasonable efforts. The fix is documentation — requiring the vendor to formalize what already exists.
The vendor has meaningful gaps. Encryption isn’t consistent, incident response hasn’t been tested, subcontractors are untracked. These gaps require negotiation with the current vendor or a structured transition to a more capable provider.
The vendor has never thought about this at all. The vendor serves multiple industries and has no healthcare or legal-specific compliance framework. The written agreement says nothing about confidentiality. There is no incident response plan. This situation requires the most urgent attention.
In all three cases, the value of the evaluation is the same: your firm now knows where it stands, has a documented record of having asked the right questions, and has a clear path to demonstrable compliance.
Score Your Provider Before a Problem Does It for You
Download our free Legal Technology Vendor Scorecard — a structured 20-minute assessment tool that walks through each of the six evaluation areas above, produces a written compliance score for your current provider, and identifies the specific gaps your firm needs to address.
When you’re ready to go further, our team offers a free IT Vendor Compliance Review — a structured evaluation of your current provider against ABA Rule 1.6 standards, with a written report delivered to your firm identifying your compliance posture and the steps needed to close any gaps.

