Pharmacy POS Vendor Security Risk Assessment Checklist

Kevin Henry

Risk Management

Published Updated

10 minutes read
Share this article
Pharmacy POS Vendor Security Risk Assessment Checklist

A pharmacy point-of-sale system may connect payment terminals, prescription workflows, inventory tools, remote support, and cloud services. Before onboarding a vendor, map those connections and assess the risks to patient information and payment data separately.

How should pharmacies classify and assess POS vendors before onboarding?

Start by defining what the vendor does, what systems it can reach, and what information it handles. A vendor that only sells software without access to protected health information (PHI) may have a different HIPAA relationship from one that hosts patient data or remotely troubleshoots systems containing it. HHS explains when a software or IT vendor may be a business associate in its Business Associate FAQ.

  • Map services and connections: Identify the POS application, payment terminals, networks, cloud hosting, integrations, support channels, and locations in scope.
  • Classify the vendor’s role: Determine whether it creates, receives, maintains, or transmits PHI or electronic protected health information (ePHI) on the pharmacy’s behalf, or can access systems containing it.
  • Rate risk before granting access: Consider the sensitivity and volume of data, vendor access privileges, remote connectivity, service criticality, and the consequences of an outage or compromise.
  • Review the service chain: Identify hosting providers, remote-support firms, payment processors, and other subcontractors that may handle data or access the environment.
  • Set approval conditions: Document required safeguards, evidence, contract terms, unresolved risks, and who may accept any remaining risk.

HIPAA requires covered entities and business associates to conduct a risk analysis of risks and vulnerabilities to ePHI; HHS says the analysis should be documented and updated as circumstances change. Use the pharmacy’s documented risk-management process to decide whether the vendor’s safeguards are appropriate before go-live. See HHS guidance on HIPAA risk analysis.

Which patient and payment data does the POS system handle and store?

Ask the vendor for a data-flow diagram and a field-level inventory, not simply a list of product features. Trace information from the terminal through the POS software, integrations, processor, backups, logs, exports, and support tools. Confirm which party controls each stage and where data is stored or transmitted.

  • Potential patient information: Patient identifiers, prescription or transaction details, payer information, loyalty profiles, and support records. Determine whether the system links identifiable patients to health-related information and whether the vendor can access it.
  • Payment information: Cardholder data, payment tokens, transaction references, and any sensitive authentication data captured by the terminal or software.
  • Operational records: User accounts, device identifiers, access logs, diagnostic files, screenshots, and backups. These may expose sensitive information even if the main transaction database does not.

Ask which fields are retained, for how long, and how the vendor deletes data at the end of the service. Confirm that diagnostic or support logs do not inadvertently capture patient or payment details. Under PCI DSS, sensitive authentication data must not be stored after authorization, even if encrypted; see the PCI Security Standards Council’s guidance on sensitive account data.

Keep the HIPAA and payment-data inventories distinct. A card payment record is not automatically ePHI simply because it was created at a pharmacy; assess whether it contains or is linked to individually identifiable health information and how it is used in the pharmacy’s operations.

How can pharmacies verify vendor access controls and security testing?

Request evidence showing how the vendor limits, authenticates, reviews, and removes access. Review both the vendor’s workforce access and the pharmacy’s own administrative accounts.

  • Ask for role and permission descriptions, unique-user account practices, privileged-account controls, and procedures for disabling access when staff leave or change roles.
  • Confirm whether multifactor authentication (MFA) is available and enforced for remote access, administrative access, and vendor support sessions. HIPAA requires authentication procedures but does not name one universal technology; the pharmacy should use its risk analysis to assess whether MFA is needed for the POS environment. See HHS guidance on authentication.
  • Review how support access is approved, limited in time, recorded, and terminated, and whether the pharmacy can disable or revoke it.
  • Request summaries of recent independent security testing, including the systems and versions tested, scope, findings, and remediation status. Ask for evidence of penetration-test remediation, not just a statement that testing occurred.
  • Ask how the vendor handles vulnerability reports, software updates, unsupported components, and security issues in subcontractor products.

Evaluate test scope and unresolved findings against the actual POS service you plan to use. A report covering a different product, hosting environment, or version may not establish the security of your deployment.

What encryption, logging, and monitoring safeguards should be reviewed?

Verify safeguards at each point where ePHI or payment data is stored, processed, or transmitted. Ask the vendor to explain which protections it operates and which the pharmacy must configure or maintain.

  • Encryption: Review protection for data in transit and at rest, key ownership and rotation, and whether encryption covers backups and exports. Confirm how keys are protected and who can access them.
  • Audit logging: Determine whether the system records relevant user and administrator activity, access to ePHI, configuration changes, and security events. Ask who reviews alerts, how investigations are documented, and how logs are protected from alteration.
  • Monitoring and response: Review alert coverage, escalation paths, after-hours response, and how the pharmacy is notified about suspicious activity affecting its systems or information.
  • Integrity and availability: Ask how the vendor detects unauthorized changes, protects system configurations, and maintains service during outages.

HIPAA’s technical safeguards address access controls, audit controls, authentication, and transmission security. Encryption specifications are designated “addressable,” which requires a reasoned assessment and appropriate documentation—not simply ignoring encryption. Review the current text of 45 CFR § 164.312 and the pharmacy’s Security Rule risk analysis.

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 should pharmacies assess POS devices and PCI DSS scope?

Map the payment flow from card entry through authorization, settlement, and any storage. Include terminals, POS workstations, management consoles, network connections, remote-support tools, and systems that can affect the security of the cardholder data environment (CDE).

Payment terminals that capture payment card data are part of the CDE and are in scope for PCI DSS. A device’s approval or a vendor’s claim that it is “PCI compliant” does not, by itself, establish the scope or compliance of the pharmacy’s environment. Review the PCI SSC guidance on payment terminals and ask the pharmacy’s acquirer or a Qualified Security Assessor (QSA) to help confirm scope where needed.

  • Record each terminal model, software version, location, connection type, and party responsible for configuration, updates, and physical security.
  • Identify whether the system stores, processes, or transmits cardholder data, and whether connected systems can access or affect the CDE.
  • If relying on network segmentation to reduce scope, request evidence that the separation is implemented and works as intended.
  • Review the vendor’s PCI DSS Attestation of Compliance (AOC), if available, and confirm that the assessed services and requirements match the services the pharmacy uses.
  • Document which applicable PCI DSS responsibilities remain with the pharmacy, vendor, processor, or another service provider.

PCI SSC states that merchants must oversee third-party service providers, perform due diligence, identify responsibility boundaries, and monitor their PCI DSS status at least annually under Requirement 12.8. The provider’s assessment evidence should cover the relevant service; an AOC or other evidence that does not cover the service in use may not be sufficient. See the PCI SSC guidance on third-party service providers and its guidance on evidence of PCI DSS compliance.

What incident response, disaster recovery, and breach-notification evidence should vendors provide?

Ask for the vendor’s incident-response and continuity procedures, then confirm that they fit the pharmacy’s operational needs. A POS interruption can affect payment operations, while an incident involving ePHI may also trigger separate HIPAA duties.

  • Request the vendor’s incident-response process for identifying, investigating, containing, and documenting security incidents, including incidents involving subcontractors.
  • Set a contractually defined notification timeframe that gives the pharmacy time to assess the event and meet its own obligations. Ask what initial and follow-up details the vendor will provide.
  • Review backup frequency, recovery objectives, restoration procedures, and results from recent recovery tests. Confirm how the pharmacy can continue essential operations during an outage.
  • Ask how evidence, logs, and affected records will be preserved and made available during an investigation.
  • Confirm how data will be returned or securely deleted at termination, including copies held by subcontractors where applicable.

When a vendor qualifies as a business associate, the BAA must address permitted uses and disclosures, safeguards, reporting, and applicable subcontractor obligations. HHS also explains that business associates must notify covered entities about breaches as required by the Breach Notification Rule. The federal rule sets an outside deadline of 60 days after discovery for business-associate notice, but a pharmacy should negotiate a shorter contractual deadline appropriate to its response needs. Review HHS BAA guidance and the HHS Breach Notification Rule.

How should pharmacies document findings and track remediation?

Keep a dated assessment record that ties each identified risk to evidence, an accountable owner, and a decision. HIPAA requires documentation of the risk analysis but does not prescribe a particular format; HHS recommends recording risk levels and corrective actions. See HHS risk-analysis guidance.

  • Record the vendor, service, data types, system connections, subcontractors, assessment date, and reviewers.
  • For each finding, document the evidence reviewed, risk rating, business impact, mitigation, owner, target date, and current status.
  • Track penetration-test remediation and other security gaps through verification and closure; document accepted risks and the reason for acceptance.
  • Retain relevant contracts, the business associate agreement (BAA) when applicable, security reports, PCI DSS evidence, and remediation records in a controlled location.
  • Set reassessment triggers such as significant system changes, new integrations, incidents, vendor changes, or newly identified risks.

There is no single HIPAA-mandated annual schedule for every POS vendor risk assessment. HHS says the Security Rule does not specify a fixed risk-analysis frequency; the process should be ongoing and responsive to changes. PCI DSS separately calls for monitoring third-party service providers at least annually. A sound assessment connects the pharmacy’s data map, vendor evidence, contract safeguards, payment scope, and remediation tracking—and revisits them when risks or services change.

FAQs

When does a pharmacy POS vendor need a business associate agreement?

A BAA is generally needed when a vendor performs a service for a HIPAA covered pharmacy that involves creating, receiving, maintaining, or transmitting PHI on the pharmacy’s behalf, or requires access to PHI to provide the service. A software sale alone does not automatically create a business-associate relationship if the vendor has no access to PHI. Determine the vendor’s actual access and service role, including remote support and hosting, and consult HHS’s Business Associate FAQ.

How can a pharmacy determine whether POS devices are in PCI DSS scope?

Trace where payment account data is captured, processed, transmitted, or stored, then identify systems connected to or able to affect those components. Payment terminals that capture card data are in scope; segmentation can reduce scope only when it effectively isolates the CDE. Confirm the pharmacy’s specific boundaries with its acquirer or a QSA, and review the PCI SSC terminal guidance.

What evidence should a pharmacy request during a vendor security assessment?

During a vendor security assessment, request a data-flow diagram, data-retention details, access-control and MFA information, security-testing scope and remediation status, incident-response and recovery procedures, subcontractor information, and relevant contract terms. For payment services, request PCI DSS evidence that covers the service being used, such as an applicable AOC or other evidence of applicable controls. Treat these as assessment evidence to review—not as proof of compliance by themselves.

How often should a pharmacy reassess its POS vendor’s security risks?

Reassess according to the pharmacy’s risk-management process, including when the vendor changes its service, data flows, access, or subcontractors, or after a relevant security incident. HIPAA does not set one fixed interval for every risk analysis; HHS describes risk analysis as ongoing. PCI DSS requires at least annual monitoring of third-party service-provider compliance status under Requirement 12.8. See HHS guidance and PCI SSC guidance.

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