A Healthcare SEO Marketing Agency’s Guide to Security Risk Assessments
Healthcare SEO depends on websites, analytics, forms, call tracking, customer relationship management (CRM) systems, and other connected tools. When those systems create, receive, maintain, or transmit electronic protected health information (ePHI), their security belongs in the organization’s HIPAA risk analysis—not outside it just because they support marketing.
This guide explains what a security risk assessment should cover, how marketing technology can introduce risk, and how to use the Security Risk Assessment Tool as an aid rather than proof of compliance. An agency’s role depends on what information it handles and on whose behalf; a healthcare organization remains responsible for assessing its own environment.
What HIPAA requires from security risk assessments
The HIPAA Security Rule requires covered entities and business associates to conduct an accurate and thorough assessment of potential risks and vulnerabilities to the confidentiality, integrity, and availability of the ePHI they hold. It also requires risk management: implementing security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level. See 45 C.F.R. § 164.308 and HHS guidance on risk analysis.
The analysis should cover ePHI throughout its lifecycle—not only information in an electronic health record. Map what the organization creates, receives, maintains, or transmits, including information handled by relevant websites, applications, vendors, and business associates. HIPAA does not prescribe one assessment method or require use of a particular tool; the method should fit the organization and its environment.
A healthcare marketing agency is not automatically a business associate simply because it provides SEO or advertising services. Its status depends on whether it creates, receives, maintains, or transmits protected health information on behalf of a covered entity or another business associate. If it does, the parties generally need a business associate agreement (BAA), and the agency may have its own Security Rule responsibilities. A business associate agreement defines permitted uses and disclosures and requires appropriate safeguards; signing one does not, by itself, make every data use permissible.
Keep the risk analysis, identified risks, and decisions documented. Revisit the assessment when changes—such as new technologies, vendors, integrations, or newly recognized risks—could affect ePHI security. HHS’s summary of the HIPAA Security Rule currently in effect explains the rule’s documentation and safeguards requirements.
How SEO and marketing tools can expose protected health information
Tracking pixels, analytics tags, session-replay tools, advertising platforms, call-tracking services, chat widgets, form tools, and CRM integrations can collect or transmit information as visitors use a healthcare website. Depending on the setup, that information might include an identifier, a page address, a search or form event, an appointment detail, or information entered into a chat or intake form.
Risk can arise when a tool sends more data than intended, when a URL or event contains identifying details, or when a vendor receives information it is not authorized to handle. Assess the actual configuration and data flows: which scripts run, what events they record, what information leaves the site, which vendors receive it, and how long it is retained. A BAA is relevant when a vendor’s role meets the business associate definition, but it does not replace review of the tool’s settings, uses, and disclosures.
Apply care when assessing tracking technologies on public pages. HHS’s bulletin addresses regulated entities’ obligations when tracking technologies collect or disclose PHI, but it also notes that a court vacated the portion treating an IP address connected to a visit to certain unauthenticated public health pages as enough, by itself, to trigger HIPAA obligations. Do not assume that every analytics event on every public health webpage is PHI—or that tracking on public pages can never involve PHI. Assess the specific information and context. See the HHS bulletin on online tracking technologies.
For an SEO and marketing review, inventory scripts and integrations across the main site, landing pages, appointment flows, patient portals, and mobile experiences. Check whether page paths, query strings, referral data, form submissions, or chat transcripts could reveal or transmit sensitive information, and identify who can access each platform.
Which administrative physical and technical safeguards should be assessed
The HIPAA Security Rule organizes its requirements into administrative safeguards, physical safeguards, and technical safeguards. The appropriate measures depend on the organization and its circumstances; HHS describes the rule as flexible and scalable rather than a one-size-fits-all technology checklist. Review the HHS summary of the Security Rule and the relevant regulatory standards.
- Administrative safeguards: Assess security policies, assigned security responsibilities, workforce access and training, incident response, contingency planning, periodic evaluation, vendor oversight, and risk-management decisions. For marketing workflows, check how staff and agency personnel receive, use, and remove access to accounts and data.
- Physical safeguards: Review facility access, workstations, devices, and media that might contain or provide access to ePHI. Consider laptops used for remote work, unattended screens, printed materials, device disposal, and procedures for returning or removing equipment. See 45 C.F.R. § 164.310.
- Technical safeguards: Examine access controls, unique user identification, audit controls, authentication, integrity protections, and transmission security. Review permissions for analytics, advertising, web, and CRM platforms, along with logging and the handling of data sent between systems. See 45 C.F.R. § 164.312.
Some Security Rule implementation specifications are labeled “addressable,” which does not mean they can simply be ignored. The organization must assess whether the specification is reasonable and appropriate in its circumstances; if it is not, it must document that determination and implement an equivalent alternative measure when reasonable and appropriate. This is part of a reasoned assessment, not a blanket exemption from securing ePHI.
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 AssessmentHow to identify threats vulnerabilities and potential impacts
Start by mapping where ePHI could enter, move through, or leave the organization’s marketing environment. Include websites and hosting, content management systems, forms, appointment and chat services, tag managers, analytics, call tracking, advertising integrations, CRMs, email platforms, APIs, and relevant subcontractors. Record what information each system handles, who can access it, and how it is transferred or retained.
Then identify reasonably anticipated threats and the vulnerabilities that could allow those threats to affect ePHI. Examples to consider include compromised accounts, excessive permissions, misconfigured tracking tags, insecure integrations, exposed credentials, unpatched software, accidental form or file sharing, vendor incidents, and service outages. These are assessment prompts, not a claim that every listed scenario applies to every organization.
For each threat-and-vulnerability scenario, consider the potential impact on confidentiality, integrity, and availability. A disclosure could expose information to an unauthorized recipient; unauthorized changes could corrupt a form, page, or data flow; and an outage could make a website or service unavailable. HHS’s risk analysis guidance recommends identifying ePHI, threats, vulnerabilities, and existing security measures as part of the analysis.
Document the evidence behind the assessment: system and vendor inventories, data-flow notes, configuration reviews, interviews, policies, and identified gaps. The goal is to assess the organization’s actual environment, including the marketing systems that handle ePHI, rather than rely on a generic checklist alone.
How to evaluate likelihood and prioritize security risks
Estimate how likely each threat-and-vulnerability scenario is to occur and how serious its potential impact could be. HIPAA calls for consideration of the probability of potential risks, but does not prescribe a single scoring formula. A documented qualitative scale or risk matrix can help an organization apply its method consistently.
When making an estimate, consider the sensitivity and amount of information involved, how accessible the system is, the weakness that could be exploited, existing safeguards, and relevant incident or testing history. For example, a marketing integration with broad access and an unchecked data export may deserve closer attention than a tool that receives no identifying or sensitive information—but confirm that distinction by examining what the system actually sends.
Use the results to prioritize risk-management actions. For each priority, document the planned safeguard or corrective action, the responsible owner, the target date, and how the organization will verify whether the action worked. Reassess remaining risk after controls are applied, and update the analysis when the system, vendor, or data flow changes. HHS explains the distinction between risk analysis and risk management: analysis evaluates risks, while management implements measures to reduce them.
How to use the Security Risk Assessment Tool without treating it as a compliance guarantee
The Security Risk Assessment Tool was developed by the Office of the National Coordinator for Health Information Technology with HHS’s Office for Civil Rights to help organizations work through risk-assessment questions. It can support information gathering and documentation, including for smaller healthcare practices and business associates. See the official Security Risk Assessment Tool page.
The tool is optional, and completing it does not guarantee HIPAA compliance or establish that an organization complies with every part of the Security Rule. Its scope is not a substitute for the broader security program, risk management, privacy obligations, or organization-specific judgment. The tool’s own disclaimer says it is informational and is not an exhaustive or definitive source.
Use the tool as one input: answer based on verified information, involve people who understand the systems and workflows, and follow up on gaps with owners and documented actions. For marketing systems, supplement it with a current inventory of website tags, vendors, integrations, access rights, and data flows. A completed tool is evidence of an assessment process—not a compliance certificate or substitute for safeguards.
In short, a useful assessment connects the HIPAA Security Rule to the real systems that handle ePHI, including SEO and marketing technology. Identify the risks, select and document appropriate safeguards, and treat any assessment tool as support for—not proof of—an ongoing security program.
FAQs
Who must conduct a HIPAA security risk assessment?
Covered entities and business associates must conduct an accurate and thorough risk analysis of the ePHI they hold. A marketing agency’s obligations depend on whether it creates, receives, maintains, or transmits protected health information on behalf of a covered entity or business associate. The organization can use internal staff, outside expertise, or both, but remains responsible for its own assessment.
What should a healthcare marketing agency include in a risk assessment?
Assess the agency’s relevant data flows and systems, including websites, landing pages, forms, analytics, pixels, call tracking, chat, CRM and advertising integrations, hosting, vendor access, and subcontractors. Identify what information each system collects or transmits, who can access it, applicable BAAs, potential threats and vulnerabilities, existing safeguards, and actions to address identified risks. Tailor the assessment to the agency’s actual role and the client’s environment.
Can website analytics expose protected health information?
They can, depending on the information collected, the website context, and how data is configured and shared. Analytics or tracking tools may receive identifiers, page or event details, or information entered into a form or portal. Review what the tools actually collect and disclose. HHS’s tracking bulletin includes a court-vacatur notice concerning a specific interpretation involving IP addresses and certain unauthenticated public webpages, so avoid treating every public-page analytics event as automatically PHI.
Does the Security Risk Assessment Tool guarantee HIPAA compliance?
No. The tool can help guide and document a risk assessment, but HHS says its use is neither required nor a guarantee of compliance. Organizations must also address the risks they identify and meet the other applicable requirements of the HIPAA Security Rule.
Table of Contents
- What HIPAA requires from security risk assessments
- How SEO and marketing tools can expose protected health information
- Which administrative physical and technical safeguards should be assessed
- How to identify threats vulnerabilities and potential impacts
- How to evaluate likelihood and prioritize security risks
- How to use the Security Risk Assessment Tool without treating it as a compliance guarantee
- 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