Speech-Generating Device Supplier Security Risk Assessment Checklist
What security risks should an assessment cover?
Assess the complete path of data through the speech-generating device, its companion apps, cloud services, and support systems. Speech recordings, transcripts, saved phrases, user profiles, and diagnostic logs may contain identifiable health information depending on their content and context.
- Map data flows: Identify what information the device collects, where it is stored, when it is transmitted, who can access it, and how long the supplier and its service providers retain it.
- Review confidentiality risks: Consider device loss or theft, unauthorized accounts, excessive staff access, insecure integrations, and disclosure through telemetry or support workflows.
- Review integrity risks: Consider unauthorized changes to saved messages, user settings, or device software that could affect privacy, reliability, or intended operation.
- Review availability risks: Assess outages, ransomware, network interruptions, and the loss of cloud or communication services. Consider the practical impact if a user cannot access their configured vocabulary or communication functions.
- Check the full supplier chain: Identify hosting providers, analytics services, subcontractors, and other parties that may handle data or provide software components.
- Evaluate the organization’s own environment: Include device configuration, Wi-Fi and network access, account provisioning, physical storage, and staff procedures.
For organizations subject to HIPAA, the Security Rule calls for an accurate, thorough assessment of risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information (ePHI). The assessment should cover ePHI wherever it is created, received, maintained, or transmitted—not only information in a cloud account. See HHS OCR’s Guidance on Risk Analysis.
How should suppliers protect speech and personal data?
Ask the supplier to explain how its safeguards work in practice for data on the device, in companion apps, during transmission, and in cloud storage. Safeguards should match the data’s sensitivity and the risks identified in your assessment.
- Limit collection and retention: Confirm whether audio is recorded or stored, whether speech is processed locally or remotely, and whether diagnostic or usage data includes identifiers. Ask how users or administrators can delete data and what happens to backups.
- Control access: Look for unique user accounts where appropriate, role-based permissions, strong authentication for administrative access, prompt removal of former users, and access logging.
- Review encryption at rest and in transit: Ask which data is encrypted, where encryption applies, and how keys are protected and managed. HIPAA’s encryption specifications are addressable—not a universal, stand-alone mandate to use one particular encryption method—so regulated organizations must assess whether encryption is reasonable and appropriate and document their decisions. See HHS OCR’s guidance on encryption under the Security Rule.
- Confirm permitted uses: Ask whether speech or usage data is used for analytics, product improvement, or other purposes, and whether those uses can be limited or disabled.
- Clarify HIPAA responsibilities: If the supplier creates, receives, maintains, or transmits PHI on behalf of a covered entity or business associate, determine whether the relationship requires a HIPAA business associate agreement. The agreement should address permitted uses, safeguards, subcontractors, and incident reporting; not every device supplier automatically has business associate status. See HHS OCR’s Business Associates guidance.
Request enough detail to assess the supplier’s protected health information safeguards, including how it handles access, backups, deletion, and third-party services. A general statement that data is “secure” does not explain which safeguards apply to your configuration.
How are devices and software updates secured?
Review both the device’s built-in protections and the supplier’s process for maintaining software throughout the product’s supported life. Ask who can change device settings, install software, or access the device remotely.
- Secure configuration: Check whether default credentials can be changed, unnecessary services can be disabled, and administrative access can be restricted. Ask how the supplier supports secure setup and configuration changes.
- Authenticate updates: Ask whether updates are restricted to authorized parties and whether the device verifies an update’s source and integrity before installation. Firmware signing is one way to verify that an update is authentic; ask how signature checks are performed and what happens if verification fails.
- Manage update controls: Confirm how customers learn about updates, whether installation can be scheduled or controlled, how update status is recorded, and what recovery options exist if an update fails.
- Understand software components: Request a software bill of materials (SBOM), or an equivalent component inventory, to help identify third-party software and assess newly disclosed component vulnerabilities. FDA identifies an SBOM as a statutory submission requirement for qualifying cyber devices; that requirement does not automatically apply to every speech-generating device. See FDA’s Cybersecurity in Medical Devices FAQs.
- Check support life: Obtain the expected security-support period, how end-of-support is communicated, and what options are available when a device can no longer receive security updates.
NIST’s IoT device guidance describes secure, configurable update mechanisms and verifying updates before installation. FDA also publishes medical-device cybersecurity guidance; its recommendations and statutory requirements apply according to the device and regulatory circumstances. See NIST’s Software Update capability guidance and FDA’s current cybersecurity guidance for medical devices.
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 AssessmentWhat evidence should suppliers provide?
Request evidence that is specific enough to evaluate the product and services you will use. The goal is to understand the safeguards, their scope, and any limitations—not to collect a folder of generic policy statements.
- A current data-flow diagram showing device, app, cloud, support, and subcontractor connections.
- A security risk assessment or summary describing key threats, safeguards, and unresolved risks relevant to the product.
- Documentation of access controls, encryption practices, key management, logging, backup, retention, and deletion.
- Software-update procedures, authentication or firmware-signing information, supported software versions, and the product’s security-support timeline.
- An SBOM or software-component inventory, together with an explanation of how components are monitored for vulnerabilities.
- A vulnerability disclosure policy, incident-response process, and customer notification procedures.
- Relevant independent assessment reports or certifications, with their scope and dates. Treat these as supporting evidence, not as proof that your specific deployment is compliant or risk-free.
- A completed security questionnaire and, where PHI handling makes it applicable, a proposed HIPAA business associate agreement.
For a qualifying cyber device, FDA describes specific cybersecurity submission requirements, including an SBOM. For devices outside that scope, an SBOM may still be useful evidence to request as part of procurement. See FDA’s explanation of cyber-device SBOM requirements.
How should incidents and vulnerabilities be managed?
Before purchase, agree on how the supplier will receive reports, investigate issues, communicate with your organization, and provide fixes or mitigations. Responsibilities and communication routes should be clear for both suspected data incidents and product vulnerabilities.
- Set reporting contacts and channels: Confirm how your team can report a suspected incident or vulnerability and how the supplier will acknowledge and triage it.
- Agree on response expectations: Define contractual timelines for initial notice, status updates, investigation findings, and mitigation plans. These terms should fit your operational needs and applicable legal duties.
- Plan for containment and recovery: Ask how the supplier can limit access, disable an affected service if necessary, restore data or operation, and support your investigation.
- Request coordinated disclosure: A vulnerability disclosure policy should explain how researchers and customers can submit reports, how the supplier evaluates issues, and how affected customers learn about fixes or workarounds.
- Check third-party coordination: Determine how the supplier tracks and addresses vulnerabilities in software components and coordinates fixes with relevant subcontractors.
- Clarify PHI breach responsibilities: If a business associate relationship applies, the business associate agreement should address reporting security incidents and breaches as required. The agreement should also specify practical notification and cooperation expectations.
FDA’s guidance for qualifying cyber devices addresses plans to monitor, identify, and address postmarket vulnerabilities, including coordinated vulnerability disclosure. FDA’s postmarket recommendations also discuss monitoring and addressing vulnerabilities over the device lifecycle. See FDA’s cybersecurity FAQs and FDA’s Postmarket Management of Cybersecurity guidance.
How can organizations document and review supplier risk?
Keep a record of the decision, the evidence reviewed, the risks you identified, and any safeguards or contract terms required before deployment. Assign an owner for each open issue and document whether it must be resolved before purchase or can be managed through a time-bound action plan.
- Record the assessment scope: Note the product model, software version, services, data types, user groups, integrations, and subcontractors included in the review.
- Rate and track risks: Document likelihood, potential impact, existing safeguards, remaining risk, mitigation owner, and target date.
- Preserve supplier evidence: Keep relevant contracts, assessments, update commitments, support dates, incident contacts, and review findings together.
- Set review triggers: Reassess when the supplier changes its data practices, cloud provider, subcontractors, software, update process, or support status, and after significant incidents or newly identified risks.
- Review periodically: Set a schedule that reflects the sensitivity of the data and the device’s role in your environment. For HIPAA-regulated organizations, HHS describes risk analysis and risk management as ongoing processes, with security measures reviewed and updated as needed. See HHS OCR’s Summary of the HIPAA Security Rule.
- Retain required documentation: HIPAA-regulated organizations should follow the Security Rule’s documentation requirements, including applicable retention periods; HHS summarizes the six-year retention rule for required Security Rule documentation in its Security Rule overview.
In summary, assess the device’s data flows, safeguards, update and vulnerability processes, and supplier evidence; document remaining risks and revisit them when circumstances change. A structured review helps you make an informed decision about whether the supplier’s protections fit your organization’s needs.
FAQs.
What security documentation should a speech-generating device supplier provide?
Request a data-flow diagram, a product-specific security risk summary, access and encryption details, update and support policies, an SBOM or component inventory where available, a vulnerability disclosure policy, incident-response procedures, and relevant independent assessment reports. If the supplier handles PHI on your organization’s behalf, determine whether a HIPAA business associate agreement is required.
How should a supplier protect speech data stored on a device or in the cloud?
The supplier should explain what speech data it collects, whether audio or transcripts are stored, who can access them, how long they are retained, and how they can be deleted. Ask about encryption at rest and in transit, access controls, key management, backups, and the protections used by cloud providers and subcontractors. Verify that the controls match your risk assessment and applicable obligations.
How can buyers verify that device software updates are authentic?
Ask the supplier how updates are authenticated and checked for integrity before installation. For example, firmware signing can help verify that an update came from an authorized source; request documentation describing signature verification, failed-update handling, and update records. NIST recommends mechanisms that verify updates before installation in its Software Update capability guidance.
What should a supplier do after discovering a security vulnerability?
The supplier should assess the vulnerability’s impact, determine which products and software components are affected, communicate with relevant customers, and provide mitigations or a validated update as appropriate. Buyers should confirm in advance how reports are submitted, how progress is communicated, and how coordinated disclosure is handled. For qualifying cyber devices, FDA describes postmarket vulnerability planning and coordinated disclosure in its Cybersecurity in Medical Devices FAQs.
Table of Contents
- What security risks should an assessment cover?
- How should suppliers protect speech and personal data?
- How are devices and software updates secured?
- What evidence should suppliers provide?
- How should incidents and vulnerabilities be managed?
- How can organizations document and review supplier risk?
- FAQs.
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