Under HIPAA, your practice remains responsible for your vendor’s security practices. This is called liability that cannot be transferred.
What this means in practice:
- If your IT vendor experiences a breach, your practice is liable
- OCR investigators examine your vendor contracts — not just the vendor’s practices
- You cannot escape responsibility by claiming “the vendor should have secured the data”
- Patients can sue your practice for damages caused by vendor negligence
A real-world example: A medical practice hired an IT vendor to manage EHR backups. The vendor failed to encrypt the backup data. An attacker accessed the unencrypted backups and stole 15,000 patient records.
Who did OCR hold responsible? The medical practice.
The investigation focused on whether the practice had verified vendor compliance, required encryption, signed a BAA, and audited the vendor’s security practices. The practice couldn’t claim the vendor should have known better. The practice should have verified compliance before granting access to patient data.
What “HIPAA Compliant” Actually Means for Vendors
Many IT vendors use the phrase “HIPAA compliant” without a clear understanding of what it requires. For vendors, genuine HIPAA compliance means:
Implementing Required Security Safeguards:
- Encryption of patient data in transit and at rest
- Access controls limiting who can view patient records
- Audit logs documenting all data access
- Regular security assessments and vulnerability testing
- Documented incident response procedures
- Business continuity and disaster recovery plans
- Physical security controls protecting servers and data centers
- Ongoing employee training on HIPAA security requirements
Signing a Business Associate Agreement (BAA) — a legal contract that defines vendor responsibilities, specifies permitted uses and disclosures of PHI, requires breach notification, and allows your practice to audit vendor security practices.
Complying with OCR Audit Standards — including documented security policies, evidence of regular assessments, proof of employee training completion, and tested incident response procedures.
Many vendors skip these requirements while still claiming compliance. The 10 questions below are how you find out.
The 10 Critical Questions to Ask Your IT Vendor
Question 1: Do You Have a Signed Business Associate Agreement Ready to Execute?
A BAA is the legal foundation of every compliant vendor relationship. Without one, you have no contractual obligation requiring the vendor to protect patient data.
Good answers to listen for:
- “Yes, we have a standard BAA template that’s part of our onboarding process”
- “Our BAA has been reviewed by legal counsel to ensure full HIPAA compliance”
- “Our BAA includes specific data handling requirements and breach notification procedures”
Red flags:
- “We don’t have a BAA, but our service is compliant anyway”
- “Other clients don’t require BAAs — do you really need one?”
- “We’ll send you a BAA eventually, but you can start now”
- A heavily one-sided BAA that shifts all liability to your practice
What a compliant BAA must include: permitted uses and disclosures of PHI, vendor responsibility for security safeguards, audit log requirements, breach notification timelines, subcontractor liability, your right to audit, and data return or destruction upon contract termination.
Action item: Request the vendor’s BAA template immediately. If they don’t have one, move to a different vendor.
Question 2: What Specific Security Safeguards Do You Have in Place?
Vague answers about “being secure” indicate the vendor doesn’t understand what compliance actually requires.
Good answers to listen for:
- “We use AES-256 encryption for data at rest and TLS 1.2+ for data in transit”
- “We implement role-based access controls limiting data visibility to authorized users”
- “We maintain comprehensive audit logs of all data access, reviewed regularly”
Red flags:
- “We’re secure — trust us”
- “We follow industry best practices” (with no specifics)
- “We outsource security to our cloud provider” (without understanding what that covers)
- “We haven’t had a breach yet, so our security must be fine”
Minimum standards to verify:
- Encryption at rest: AES-256 or equivalent
- Encryption in transit: TLS 1.2 or higher
- Access controls: Role-based with MFA for privileged access
- Audit logging: Comprehensive logs of who accessed what and when
- Backup encryption: Separate from production system encryption
Action item: Request the vendor’s security documentation. Vague answers or refusal to share details is a serious red flag.
Question 3: Have You Undergone HIPAA Security Audits or Third-Party Certifications?
Third-party assessments provide independent verification of compliance. Reputable vendors undergo SOC 2 Type II audits or equivalent assessments validating their HIPAA controls.
Good answers to listen for:
- “We maintain SOC 2 Type II certification”
- “We undergo annual security audits by independent third parties”
- “We can provide audit reports under NDA demonstrating our security controls”
Red flags:
- “We’ve never had an audit, but we’re definitely compliant”
- “Our management says we’re secure” (internal assessment only)
- Vendor cannot produce any third-party security verification
Certifications that matter:
- SOC 2 Type II — Independent audit of security controls over time
- HITRUST CSF — Healthcare-specific security certification
- ISO 27001 — Information security management certification
- Penetration testing reports — Independent vulnerability assessments
Action item: Request copies of third-party audit reports. Review the date — old audits may not reflect current practices. Refusal to share audits puts their claimed compliance in serious doubt.
Question 4: How Do You Handle Data Encryption?
Encryption of patient data — both stored and transmitted — is a non-negotiable HIPAA requirement.
Good answers to listen for:
- “We encrypt all patient data at rest using AES-256”
- “Data in transit is encrypted using TLS 1.2 or higher”
- “Backup data is encrypted using the same standards as production data”
- “Encryption keys are managed separately from encrypted data”
Red flags:
- “We don’t encrypt because it slows performance”
- “We encrypt some systems but not others”
- “We’re not sure about our encryption — IT handles that”
- Use of outdated standards: SSL 3.0, WEP, or DES
Standards to insist on:
- At rest: AES-256 minimum
- In transit: TLS 1.2 or higher (TLS 1.3 preferred)
- Key management: Encryption keys stored separately; rotated regularly
Action item: Request the vendor’s encryption documentation. If they use outdated standards or cannot provide specifics, demand an upgrade — or change providers.
Question 5: What Is Your Incident Response Procedure If There’s a Security Breach?
When a breach occurs, vendors must notify your practice immediately. HIPAA requires notification “without unreasonable delay.” Vendors without defined response procedures create notification delays that compound both your compliance exposure and your recovery timeline.
Good answers to listen for:
- “We have documented incident response procedures”
- “We notify clients within 24 hours of detecting a breach”
- “We preserve forensic evidence and provide detailed breach reports”
- “Our BAA specifies breach notification timelines”
Red flags:
- “We’ll let you know if we have a breach, but no specific timeline”
- “We decide internally who needs notification”
- “We don’t have a formal incident response process”
- Breach notification happens after legal review — weeks or months later
What a strong incident response plan covers:
- Immediate breach detection and containment
- Practice notification within 24 hours
- Specific details: affected data, patient count, breach timeline
- Professional forensic investigation preserving evidence
- Regulatory notifications as required
- Full incident documentation
Action item: Request the vendor’s incident response plan. No plan, or refusal to share it, is a major compliance red flag.
Question 6: Who Are Your Subcontractors — and Do They Have BAAs?
Your vendor may outsource services to third parties. Each subcontractor handling patient data must also sign a Business Associate Agreement. Use of unapproved subcontractors is itself a HIPAA violation.
Good answers to listen for:
- “We maintain a complete list of subcontractors with access to patient data”
- “All subcontractors sign BAAs before accessing any PHI”
- “We notify you when subcontractors change”
Red flags:
- “We’re not sure who our subcontractors are”
- “Our subcontractors are covered by our BAA” — they need their own
- “We use cloud storage providers but haven’t verified their compliance”
Common subcontractors to verify:
- Cloud storage providers (AWS, Azure, Google Cloud)
- Data backup vendors
- Remote access and VPN providers
- Email management services
- Disaster recovery partners
- Help desk or support contractors
Action item: Request the vendor’s full subcontractor list. Verify each one has a signed BAA. If subcontractors aren’t documented, demand accountability or change vendors.
Question 7: How Do You Handle Backups and Disaster Recovery?
Patient data must be backed up regularly, encrypted, and verified as restorable. Many practices carry significant exposure because their vendor’s backups were never properly tested.
Good answers to listen for:
- “We conduct daily incremental and weekly full backups”
- “All backups are encrypted separately from production systems”
- “We test backup restoration quarterly”
- “Our RTO is [specific timeframe]; our RPO is [specific timeframe]”
- “Backups are stored in geographically redundant locations”
Red flags:
- “We have backups but haven’t tested restoration recently”
- “Backup testing happens rarely or never”
- “All backups are stored in one location”
- “We’re not sure where backups are stored”
- “We don’t have a formal disaster recovery plan”
Backup requirements to verify:
- Frequency: Daily incremental minimum; weekly full
- Encryption: Same standard as production data
- Testing: Quarterly restoration tests minimum
- Geographic redundancy: Multiple storage locations
- Retention policy: Aligns with regulatory requirements
Action item: Ask the vendor to restore a sample backup while you observe. If they can’t demonstrate successful restoration, that is a critical compliance gap.
Question 8: What Employee Training Do You Require for HIPAA Compliance?
HIPAA requires vendors to train employees on security obligations and confidentiality requirements. Vendors without formal training programs create significant insider threat exposure.
Good answers to listen for:
- “All employees receive HIPAA training before accessing patient data”
- “We conduct annual HIPAA refresher training and track completion”
- “We run regular phishing awareness training and employee testing”
Red flags:
- “Employee training is optional”
- “We mention HIPAA briefly during onboarding”
- “Employees are assumed to know what HIPAA requires”
- No documentation of training completion
A complete training program covers:
- HIPAA security requirements and why they matter
- Password policies, encryption, and access controls
- Breach recognition and reporting procedures
- Employee confidentiality agreements
- Phishing awareness and simulation testing
- Annual recertification at minimum
Action item: Request training program documentation and completion rates for current employees. If the vendor cannot demonstrate comprehensive, documented training — that’s a compliance gap.
Question 9: How Do You Manage Access Controls and User Authentication?
HIPAA requires that only authorized personnel can access patient data. Access controls must both limit visibility by role and produce audit trails showing who accessed what and when.
Good answers to listen for:
- “We implement role-based access control limiting data access by job responsibility”
- “Multi-factor authentication is required for all privileged access”
- “Each user has unique credentials — no shared passwords”
- “Access is revoked immediately upon employee termination”
- “Audit logs are monitored regularly for suspicious activity”
Red flags:
- “Everyone on our team has the same credentials”
- “We don’t track who accesses what data”
- “We don’t monitor access logs”
- “Former employees sometimes still have active system access”
- “MFA isn’t necessary for our service”
- “Audit logging is disabled for performance reasons”
Action item: Request access control procedures and sample audit logs. Ask specifically how they handle access removal for terminated employees. Weak or poorly documented access controls represent a significant vulnerability.
Question 10: Do You Have Cyber Insurance Covering Breach Notification Costs?
Cyber insurance covering breach investigation, notification, and remediation protects your practice from financial devastation if the vendor is compromised. Vendors with no coverage — or inadequate coverage — create uninsured liability exposure for your practice.
Good answers to listen for:
- “We maintain comprehensive cyber liability insurance”
- “Our policy covers breach investigation, forensic costs, and notification”
- “We can provide proof of current coverage”
- “Our coverage includes HIPAA-specific breach requirements”
Red flags:
- “We don’t have cyber insurance — haven’t needed it”
- “We’re not sure what our insurance covers”
- “Our insurance excludes healthcare-related breaches”
- “We can’t provide proof of coverage”
Coverage that matters:
- Breach investigation and forensic examination
- Notification to affected individuals
- Credit monitoring and identity protection services
- Legal defense fees
- Regulatory fine coverage (varies by state)
- Coverage limits adequate for the vendor’s client base and data volume
Action item: Request the vendor’s cyber insurance declarations page. Verify coverage is active and adequate. No insurance or inadequate coverage is a compliance risk your practice carries directly.
Quick Reference: IT Vendor HIPAA Compliance Scorecard
| Evaluation Area | Green ✅ | Yellow ⚠️ | Red ❌ |
|---|---|---|---|
| Business Associate Agreement | Signed, current BAA in place | BAA available but not yet signed | No BAA or refuses to sign |
| Encryption at Rest | AES-256 or equivalent | Older but functional standard | No encryption or outdated standard |
| Encryption in Transit | TLS 1.2 or higher | Older TLS versions | No encryption or SSL/outdated |
| Security Audit/Certification | SOC 2 Type II or HITRUST | Internal assessment only | No audits or certifications |
| Incident Response Plan | Documented, tested, <24hr notification | Plan exists but untested | No formal incident response plan |
| Subcontractor BAAs | All subcontractors documented with BAAs | Some subcontractors covered | Subcontractors untracked or uncovered |
| Backup & Disaster Recovery | Daily backups, quarterly testing, encrypted | Backups exist with minimal testing | No backups or never tested |
| Employee Training | Annual HIPAA training, fully documented | Training inconsistent or optional | No formal training program |
| Access Controls & MFA | RBAC with MFA for privileged access | Basic access controls only | Shared passwords or no controls |
| Cyber Insurance | Active coverage verified | Minimal or outdated coverage | No insurance or inadequate coverage |
Red Flags That Require Immediate Action
If your current IT vendor exhibits any of the following, do not delay in addressing it:
- No signed Business Associate Agreement — this is a legal requirement, not optional
- Refuses third-party audits or certifications — legitimate vendors can demonstrate compliance
- Uses outdated encryption — SSL 2.0, WEP, or DES are major unacceptable vulnerabilities
- Cannot describe security controls specifically — vague answers indicate a lack of real compliance
- Shared passwords or no access controls — a fundamental security failure
- No incident response procedure — breach notification will be delayed or inadequate
- Subcontractors without BAAs — liability is not properly managed
- Backups never tested or unencrypted — data loss or breach risk is unquantified
- No employee HIPAA training program — insider threat exposure is unaddressed
- No cyber insurance — financial liability from a breach is entirely uncovered
Making a Vendor Change
If your evaluation leads you to change IT vendors, follow these steps to protect your practice through the transition:
- Do not terminate the existing vendor until the replacement is fully operational
- Verify the new vendor has a signed BAA ready before migration begins
- Ensure all data migration procedures are secure, documented, and verified
- Confirm all data is securely deleted from the old vendor after successful migration
- Verify backup and disaster recovery functions correctly with the new vendor
- Update your cyber insurance with the new vendor’s information
- Document the entire transition process for compliance purposes
Don’t Wait for a Breach to Find Out
Your IT vendor’s security practices directly determine whether your practice remains HIPAA compliant. You cannot transfer that liability to the vendor. OCR holds you accountable.
The 10 questions and scorecard in this guide give you the specific, actionable criteria to evaluate your current provider — or any new vendor you’re considering. Many medical practices are operating right now with IT vendors who fail several of these criteria without realizing the exposure it creates.
At AI Managed IT Services, we specialize in HIPAA-aligned IT management for medical practices across greater Los Angeles. Our free IT Vendor Compliance Review evaluates your current provider against the standards in this guide — covering your BAA status, encryption practices, access controls, backup readiness, incident response capability, and more — and gives you a clear, prioritized picture of where your practice stands. Don’t wait for an OCR audit to find out. Get the 16 Critical Questions Guide or call 310-444-4343 for a free vendor compliance review today.
Know exactly where your vendor stands before a breach forces the question.

