Dental Cone Beam CT Vendor Security Risk Assessment Guide

Kevin Henry

Risk Management

Published Updated

10 minutes read
Share this article
Dental Cone Beam CT Vendor Security Risk Assessment Guide

What safeguards should a dental CBCT vendor demonstrate for ePHI?

Ask how the vendor protects electronic protected health information (ePHI) across the CBCT scanner, acquisition workstation, imaging software, support tools, and any hosted services. Request written evidence of security policies, risk assessments, access controls, audit logging, workforce training, backup and recovery procedures, and vulnerability management. A vendor’s “HIPAA-compliant” statement or a certification alone does not establish that your practice has met its own obligations.

Confirm whether vendor personnel can view or handle identifiable scans during installation, remote support, troubleshooting, or cloud hosting. If the vendor creates, receives, maintains, or transmits ePHI on your behalf, determine whether a business associate agreement (BAA) is required. HHS explains that a software provider that accesses patient information to provide its service may be a business associate; simply selling software without access to PHI does not by itself create that relationship. Review HHS guidance on software vendors and business associates.

  • Identity and access: Ask about unique user accounts, role-based access control, least-privilege permissions, multifactor authentication for remote or administrative access, and prompt removal of accounts when access is no longer needed.
  • Logging and monitoring: Verify that access to images and administrative functions is logged, that logs can be reviewed, and that the vendor explains how suspicious activity is detected and investigated.
  • Data handling: Identify what patient data the vendor collects, where it is stored, how long it is retained, which subcontractors can access it, and how it is returned or securely deleted when service ends.
  • Evidence: Request relevant security assessment summaries, penetration-test summaries, vulnerability-management procedures, incident-response documentation, and independent audit reports, with sensitive details appropriately redacted.

For a vendor acting as a business associate, the BAA should specify permitted uses and disclosures, safeguards, incident reporting, subcontractor requirements, and what happens to PHI when the agreement ends. See HHS sample business associate agreement provisions. Treat reports such as SOC 2 or ISO certificates as supporting evidence to assess—not as a substitute for your risk analysis, contract review, or confirmation that the report covers the services you use.

How do you inventory CBCT devices and connected imaging systems?

Start with a complete inventory of the equipment, software, services, and pathways that create, display, store, or transmit CBCT images and associated patient information. HHS identifies systems and applications used to access or house ePHI, including vendor systems, as relevant to risk analysis. See HHS guidance on risk analysis and system inventories.

  • Record the scanner manufacturer, model, serial number, location, network connection, support status, and CBCT firmware version.
  • Include acquisition and reconstruction workstations, imaging software, operating systems, databases, local storage, and removable media.
  • Map connections to the practice-management system, EHR, PACS or image archive, DICOM gateway, printers, backup systems, cloud storage, and any connected imaging modalities.
  • Document vendor remote-access pathways, support accounts, VPNs, remote-management software, and the personnel authorized to use them.
  • Identify data flows: what information moves, where it goes, how it is protected, who can access it, and how it is retained or deleted.

For each asset, record an owner, business purpose, software and firmware versions, support or end-of-life status, and risk rating. Keep the inventory current when equipment, integrations, vendor access, or network configurations change; it should inform the practice’s broader risk analysis rather than exist as a stand-alone list.

How should you assess vendor penetration testing and incident response plans?

Ask whether the vendor tests the CBCT product and the services that handle its data, and request a recent summary showing the test date, scope, testing method, independent tester qualifications, key findings, and remediation status. Clarify whether testing covered the device firmware, management interfaces, remote-support tools, imaging software, cloud environment, and relevant interfaces. FDA states that cybersecurity testing—including vulnerability assessment and penetration testing—is the medical device manufacturer’s responsibility. See FDA cybersecurity resources for medical device manufacturers.

A penetration-test report is a snapshot, not a guarantee that a system is secure. Ask how the vendor tracks newly discovered vulnerabilities, assigns remediation priorities, retests fixes, and communicates unresolved risks. Confirm whether the practice can receive notice of security issues affecting its specific CBCT model, software version, or hosted service.

Review the vendor’s incident response plan for clear points of contact, escalation paths, investigation and containment steps, evidence preservation, service restoration, and coordination with your practice. Ask how quickly the vendor will notify you of suspected incidents and what information it will provide. HIPAA requires business associates to identify and respond to security incidents, mitigate harmful effects when practicable, and document incidents and outcomes; the BAA must address reporting. See HHS guidance on business associate security-incident duties.

Set contractual notification timelines that give your practice enough time to assess the event and meet its own obligations. HIPAA’s Breach Notification Rule sets a maximum outside deadline for a business associate’s notice to a covered entity in applicable cases; that deadline should not be treated as a target response time. Review HHS breach notification guidance.

Ready to assess your HIPAA security risks?

Join thousands of organizations that use Accountable to identify and fix their security gaps.

Take the Free Risk Assessment

How can you verify encryption and imaging-data interoperability?

Ask the vendor to describe encryption in transit and at rest for every location where ePHI may exist, including scanner storage, workstations, backups, cloud services, support sessions, and transfers between systems. Request configuration details, supported protocols, key-management responsibilities, and evidence that encryption is enabled in your deployment. Where possible, verify settings directly and test transmission paths with your IT or security team.

HIPAA requires technical safeguards for access control and transmission security, while encryption specifications in the Security Rule are Addressable. “Addressable” does not mean optional: the regulated entity must assess whether the specification is reasonable and appropriate, implement it when it is, or document why it is not and use an equivalent alternative measure when reasonable and appropriate. Consult 45 CFR § 164.312 and HHS risk analysis guidance.

For imaging data interoperability, ask which DICOM services, transfer syntaxes, and image objects the system supports, and test representative studies through the practice’s actual workflow. Verify that images and required patient or study information can be exported, imported, viewed, and archived in the systems you use, without losing necessary data. DICOM is designed to facilitate interoperability among medical imaging equipment; see the DICOM Standard’s scope and field of application.

Test secure transfers to and from the CBCT system, including failure handling, access permissions, and audit trails. Confirm that diagnostic access, image export, and vendor support do not create unintended copies or bypass the practice’s security controls.

What security patching and vendor reviews should you schedule?

Set a documented, risk-based review schedule for CBCT firmware, operating systems, imaging applications, connected services, and vendor security practices. HIPAA does not prescribe one universal patching interval or annual vendor-review schedule; the practice should determine timing based on its risk analysis, the device’s clinical role, vendor advisories, and the urgency of identified vulnerabilities. HHS says risk analysis is ongoing and should be updated as circumstances require. See HHS guidance on ongoing risk analysis.

  • Check vendor security advisories and the device’s support or end-of-life status on a defined recurring basis and when a relevant alert is issued.
  • Record the current CBCT firmware version and software versions, available updates, known vulnerabilities, and any documented reason for delaying a patch.
  • Before applying updates, coordinate with the manufacturer and assess patient-safety, imaging, compatibility, backup, and rollback considerations.
  • After installation, verify the system’s operation, security settings, network connections, and ability to exchange and retrieve imaging data.
  • Reassess the vendor after material changes, such as a new hosting arrangement, subcontractor, remote-access method, product version, or security incident.

FDA recommends lifecycle management of medical-device cybersecurity, including monitoring and addressing vulnerabilities, and advises healthcare delivery organizations to work with manufacturers when considering device updates. See FDA postmarket cybersecurity guidance. Keep records of review decisions, compensating controls, vendor responses, and assigned follow-up actions.

Which compliance obligations apply to CBCT data storage and access?

HIPAA obligations depend on the organizations and services involved, not simply on whether a system is a CBCT scanner. A dental practice that is a covered entity must protect ePHI it creates, receives, maintains, or transmits. If a vendor handles that information on the practice’s behalf, determine whether the vendor is a business associate and, if so, put the required written agreement in place. HHS explains the roles of covered entities and business associates.

The Security Rule requires an accurate and thorough risk analysis, risk management, appropriate safeguards, and regular review of information-system activity. It also includes access-control, audit-control, authentication, and transmission-security standards. Apply role-based access control so staff and vendor personnel receive only the access needed for their duties, and review user accounts and logs as part of practice procedures. See 45 CFR § 164.308 and 45 CFR § 164.312.

Document how images are stored, backed up, accessed, shared, retained, and securely disposed of. Confirm that the vendor’s contract and technical settings match the practice’s policies, including authorized uses, incident reporting, subcontractors, and data return or destruction. Other federal or state requirements may apply depending on the parties, service, and jurisdiction, so assess those separately rather than assuming HIPAA is the only applicable obligation.

A sound CBCT vendor assessment combines a current asset and data-flow inventory, documented safeguards, tested incident and patching processes, verified encryption and interoperability, and clear contracts. Revisit the assessment when your systems or vendor arrangements change, and document how identified risks are addressed.

FAQs

What security documents should a dental CBCT vendor provide?

Request security policies or control summaries, a recent penetration-test or vulnerability-assessment summary, incident response and breach-notification procedures, patch and vulnerability-management processes, backup and recovery information, and documentation of encryption, access control, logging, and remote support. Ask for relevant independent audit reports and a current list of subcontractors that may handle ePHI. If the vendor is a business associate, obtain and review a BAA; a security report or certificate does not replace it.

How often should CBCT device firmware and software be reviewed for security updates?

Set a recurring review interval based on your risk analysis and check sooner when the vendor issues an advisory or a relevant vulnerability is disclosed. Review the CBCT firmware version, imaging software, operating system, and connected services together. Coordinate changes with the manufacturer, assess clinical and operational risks, and document update decisions. HIPAA does not establish a single universal patch-review interval.

How can a dental practice verify that CBCT data is encrypted during storage and transmission?

Ask the vendor for system-specific documentation showing where ePHI is stored and how encryption is configured for storage, backups, network transfers, and remote support. Verify settings in your own environment where possible, and test transfer paths with your IT or security team. Record any gaps, risk decisions, and alternative safeguards; HIPAA’s encryption specifications are addressable and require an appropriate documented assessment.

Which connected systems should be included in a CBCT vendor security assessment?

Include the CBCT scanner, acquisition and reconstruction workstations, firmware and imaging software, local storage, and any remote-support tools. Also map systems that exchange, store, back up, or access its images or patient data, such as the practice-management system, EHR, PACS or image archive, DICOM interfaces, network infrastructure, cloud services, and relevant connected imaging equipment. Include vendor accounts, subcontractors, and data-transfer pathways in the assessment.

Share this article

Ready to assess your HIPAA security risks?

Join thousands of organizations that use Accountable to identify and fix their security gaps.

Take the Free Risk Assessment

Related Articles