Smoking Cessation Quitline Vendor Security Risk Assessment Checklist

Kevin Henry

Risk Management

Published Updated

11 minutes read
Share this article
Smoking Cessation Quitline Vendor Security Risk Assessment Checklist

A quitline vendor security assessment should test how participant information is collected, used, accessed, shared, protected, and ultimately returned or destroyed. Use this checklist to evaluate the vendor’s safeguards and supporting evidence against your state’s contract, program requirements, and applicable laws.

First determine which rules apply. HIPAA applies to covered entities and business associates as defined by the law; providing a quitline service or handling tobacco-use information does not, by itself, establish that a vendor is subject to HIPAA. State privacy, security, breach-notification, public-records, and contract requirements may apply separately. HHS guidance on covered entities and business associates

What should a quitline vendor security assessment cover?

Define the assessment scope before reviewing controls. Document which services the vendor provides, which systems and locations support them, what participant and state data they handle, and which staff or subcontractors can access that data. Include intake, counseling, referrals, text or email communications, reporting, analytics, hosting, and technical support where relevant.

  • Request a current system and data-flow diagram showing collection points, integrations, storage locations, transfers, backups, and deletion paths.
  • Identify the vendor’s security owner, incident contact, hosting providers, support teams, and subcontractors that can access program data.
  • Review the vendor’s written information security program, risk assessment process, policies, and remediation tracking.
  • Compare the vendor’s stated controls with the actual services, contract terms, state requirements, and the sensitivity of the data.
  • Record gaps, risk ratings, owners, due dates, and any contract conditions required before data access begins.

If HIPAA applies, the Security Rule requires a risk analysis and risk management process for electronic protected health information (ePHI). A vendor’s risk assessment should therefore cover confidentiality, integrity, and availability risks across the systems that create, receive, maintain, or transmit ePHI. HHS guidance on HIPAA risk analysis

How should participant and state data be protected?

Ask the vendor to inventory the information it collects and explain why each field is needed. Quitline records may include names and contact details, tobacco-use information, health-related responses, referral details, and counseling notes. Assess how the vendor protects each data type in intake forms, databases, communications, reports, exports, and backups.

  • Check that collection, use, disclosure, and retention are limited to documented program purposes and authorized contract terms.
  • Review whether the vendor applies minimum necessary data access: staff and systems should receive only the information needed for their tasks. HIPAA’s minimum necessary standard has exceptions, so confirm its applicability to the specific use or disclosure rather than treating it as universal. HHS guidance on the minimum necessary requirement
  • Ask how data is encrypted in transit and at rest, where encryption keys are managed, and how access to keys is restricted.
  • Review protections for paper records, call recordings, messages, removable media, printed lists, and exported files, if those are part of the service.
  • Confirm safeguards for secure data transfer, including approved transfer methods, recipient verification, and controls against misdirected communications.
  • Check whether de-identified or aggregated data is used for analytics, how re-identification risk is addressed, and whether any secondary use is prohibited or requires approval.

How can access controls and personnel security be verified?

Request the vendor’s access-control policy, role matrix, and sample access-review records. A role-based access control model should link job duties to approved data access, distinguish routine staff from privileged administrators, and prevent shared accounts from obscuring who performed an action.

  • Verify unique user accounts, documented approvals, appropriate authentication safeguards, and prompt removal or adjustment of access when a worker changes roles or leaves.
  • Ask whether stronger authentication, such as multifactor authentication, is used for remote access and privileged accounts, and review exceptions and compensating controls.
  • Review how the vendor approves, time-limits, monitors, and records emergency or elevated access.
  • Check that periodic access reviews cover employees, temporary workers, contractors, and third-party support personnel.
  • Review workforce screening practices where lawful and appropriate, security and privacy training records, confidentiality obligations, and documented sanctions for policy violations.
  • Ask how call-center workspaces, remote work, screens, headsets, printed materials, and conversations are protected from unauthorized viewing or disclosure.

For organizations subject to HIPAA, the Security Rule addresses workforce security, information access management, and regular review of information-system activity. Its technical safeguards include access controls and person or entity authentication. 45 CFR § 164.308 and 45 CFR § 164.312

What incident response and state notification procedures are required?

Review the vendor’s incident-response plan and confirm it covers suspected as well as confirmed events, including unauthorized access, misdirected data, lost devices, malicious activity, service outages, and incidents at subcontractors. The plan should identify who investigates, preserves evidence, contains the event, assesses affected data, and communicates with the state program.

  • Confirm the vendor has a named, monitored incident contact and a secure method for reporting events at any time.
  • Set a contractual security incident notification timeframe that is prompt enough for the state to meet its own obligations. Specify what initial reports must include and how the vendor will provide updates as facts become available.
  • Require cooperation with investigation, containment, evidence preservation, risk assessment, remediation, and any legally required notices.
  • Confirm the vendor can identify affected records, data types, individuals, systems, locations, and relevant subcontractors.
  • Review incident logs, tabletop exercise results, lessons learned, and evidence that corrective actions were completed.
  • Check the applicable state law, grant conditions, and contract for notification duties and deadlines; do not assume one deadline applies across all states or incident types.

Where HIPAA’s Breach Notification Rule applies, a business associate must notify the covered entity of a breach of unsecured PHI without unreasonable delay and no later than 60 calendar days after discovery. That outer limit is not a substitute for a faster contractual reporting timeframe the state may need. HIPAA’s business-associate contract also addresses reporting security incidents. HHS Breach Notification Rule guidance and HHS business associate contract 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

Which technical safeguards, logs, and vulnerability tests should be reviewed?

Ask for evidence that technical controls are implemented on the systems supporting the quitline, not just a general security policy. Review the vendor’s system configuration, security monitoring, change management, and vulnerability remediation testing process, including how findings are prioritized, assigned, fixed, and retested.

  • Review safeguards for access control, authentication, secure transmission, data integrity, endpoint protection, network boundaries, and administrative access.
  • Ask what security events are logged, how logs are protected from alteration, who reviews alerts, and how long relevant records are retained.
  • Check whether logs can support an investigation by showing account activity, access to participant records, administrative actions, exports, failed logins, and security alerts, as appropriate.
  • Review recent vulnerability scan summaries and penetration-test executive summaries, including scope, test date, exclusions, severity ratings, unresolved findings, and retest evidence.
  • Confirm that vulnerability remediation testing verifies fixes rather than relying only on a vendor’s statement that an issue was closed.
  • Ask how the vendor manages security patches, unsupported software, secure development, configuration changes, and disclosure of newly discovered vulnerabilities.

HIPAA requires regulated entities to implement audit controls and to regularly review system activity; the Security Rule is technology-neutral and does not prescribe one universal testing method or product. NIST’s control guidance includes vulnerability monitoring and scanning as a way organizations can assess and manage technical risks. 45 CFR § 164.312 and NIST SP 800-53 Rev. 5

How should data retention, recovery, and subcontractors be assessed?

Compare the vendor’s retention schedule with the state’s requirements and the contract. Establish what happens to active records, archives, call recordings, exports, backups, and derived data when the service ends or a participant’s record must be deleted.

  • Document retention periods, permitted exceptions, deletion methods, and how the vendor verifies that data has been removed from systems and media.
  • Specify whether the state receives its data in a usable format on request or at contract termination, and how the vendor will support secure transfer.
  • Review the data recovery plan, backup frequency, protection of backup copies, recovery objectives, and results of restoration tests.
  • Confirm how the vendor maintains service continuity during a disruption and communicates outages that affect quitline operations or data availability.
  • Obtain a current list of subcontractors, the services they perform, the data they can access, and the locations where data is processed or stored.
  • Review subcontractor security obligations, including flow-down privacy and security terms, incident reporting, access restrictions, deletion or return of data, and the state’s approval or notice rights.

For HIPAA-covered ePHI, the Security Rule includes contingency-plan provisions addressing data backups, disaster recovery, emergency-mode operations, and testing or revision of plans. HIPAA business associate arrangements also require applicable safeguards to flow to subcontractors that handle ePHI on the business associate’s behalf. 45 CFR § 164.308 and HHS guidance on business associates and subcontractors

What compliance evidence and audit documentation should vendors provide?

Ask for current, reviewable evidence that matches the service scope. A policy or questionnaire response is useful, but it does not alone demonstrate that a control is operating effectively. Agree on how sensitive assessment materials will be shared and whether the state can request follow-up evidence or an audit under the contract.

  • Written information security program, security policies, risk assessment, remediation plan, and named security responsibility.
  • Data-flow and system diagrams, data inventory, retention schedule, and current subcontractor list.
  • Access-control procedures, sample access-review evidence, personnel training records, and incident-response plan.
  • Recent vulnerability assessment and penetration-test summaries, remediation status, and relevant retest evidence.
  • Backup and recovery procedures, restoration-test results, and business continuity documentation.
  • Relevant independent audit reports or certifications, if available, with scope, audit period, exceptions, and any bridge letter or remediation evidence needed to understand coverage.
  • Executed contract provisions covering permitted data use, security safeguards, incident reporting, subcontractor security obligations, audit cooperation, and data return or destruction.

Do not treat a report as proof that every quitline system or subcontractor is covered: verify its scope, period, exceptions, and relevance to the services under review. HIPAA does not generally require a business associate to provide a customer with audit access or security documentation, so specify any additional evidence and assessment rights needed in the contract. HHS guidance on customer access to cloud-provider security documentation

In summary, a useful assessment connects the data the quitline handles to documented safeguards, tested response and recovery capabilities, tightly controlled access, accountable subcontractors, and clear contract terms. Record unresolved risks and require specific evidence or corrective actions before approving access to participant or state data.

FAQs

What security documents should a quitline vendor provide during an assessment?

Request the vendor’s written information security program, risk assessment, data-flow diagram, data-retention schedule, access-control policy, incident-response plan, recovery-test evidence, subcontractor list, and relevant independent audit or security-test summaries. Confirm that each document covers the systems and services used for your quitline and note the document’s date, scope, exceptions, and open remediation items.

How should a vendor report a security incident involving quitline data?

The vendor should follow the incident-response process and promptly notify the state contact named in the contract, even while the investigation is ongoing. The contract should define the security incident notification timeframe, reporting channel, required initial details, update cadence, cooperation duties, and who determines legally required notifications. If HIPAA applies, a business associate’s notification for a breach of unsecured PHI is due without unreasonable delay and no later than 60 calendar days after discovery; a state contract may require earlier notice.

What safeguards should protect participant intake and tobacco-use information?

Use data minimization, secure intake and transfer methods, encryption protections, role-based access control, unique accounts, appropriate authentication, audit logging, workforce training, and safeguards for call-center workspaces and printed records. Limit collection and access to what the service needs, and confirm protections for copies, exports, messages, recordings, and backups. Apply the requirements of the relevant state law and contract, and HIPAA where the vendor’s relationship and data meet HIPAA’s definitions.

How should subcontractors’ access to quitline data be assessed?

Obtain a current list of subcontractors, their functions, data access, processing locations, and relevant security evidence. Check that contracts restrict use and disclosure, require appropriate safeguards and incident reporting, and address return or deletion of data. If HIPAA applies, the business associate must obtain applicable written assurances from a subcontractor that creates, receives, maintains, or transmits ePHI on its behalf.

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