Category: Uncategorized

  • Why a remote HIPAA risk assessment still has to know your state

    Most of the technical work in a HIPAA risk assessment can happen remotely. Sign-in logs, configuration exports, screenshots, interviews over video, and secure file exchange cover a lot. That does not mean geography stopped mattering.

    Your state still shapes breach notification clocks, consumer protection expectations, Medicaid and facility rules, and how local vendors behave. A remote assessment that ignores that context produces a generic binder.

    What remote does well

    • Microsoft 365 / Entra and cloud app review
    • Firewall and external surface checks
    • Policy and BAA gap review against how you say you operate
    • Interviews with practice managers, billing, and IT
    • Drafting a risk register with owners and priorities

    Dark Edge runs this model for independent practices on purpose. Travel is optional for many technical steps. Honesty about what still needs local context is required.

    What “your state” changes in practice

    Breach notification. HIPAA has federal timelines. Many states add their own notice rules, attorney general involvement, or shorter clocks. Your incident response plan should not pretend only the federal rule exists.

    Licensed professionals and facility types. Dental boards, medical boards, nursing facility survey culture, and substance use confidentiality overlays (think 42 CFR Part 2 where it applies) change which stories matter in the risk analysis narrative.

    Common regional vendors. The billing company, imaging vendor, or IT shop everyone in your metro uses shows up in BAAs and remote access patterns. An assessor who has never asked where you are will miss that cluster.

    Workforce reality. Rural broadband, shared clinics, and multi-site groups that cross state lines change how ePHI moves after hours.

    How to brief a remote assessor in one page

    Send, before kickoff:

    • Legal entity name, states of operation, and locations
    • EHR and major vendors
    • Whether you are a covered entity, BA, or both
    • Any open complaints, recent incidents, or cyber insurance questionnaire due dates
    • Who can authorize access and how break-glass works

    That one-pager saves a week of guessing.

    Bottom line

    Remote is a delivery method. State context is part of accuracy. A thorough HIPAA risk assessment uses both.

    If you want a fixed-scope remote assessment that still names your jurisdictions in the workpapers, we should talk before the next questionnaire lands.

  • HIPAA risk assessment for rehab, nursing homes, and assisted living (and where Hestia fits)

    Rehab centers, nursing homes, and assisted living communities sit in a hard corner of healthcare IT. Clinical systems, billing, family portals, and a workforce that shares workstations across shifts. State surveyors and HIPAA expectations both show up, often on someone else’s timeline.

    A HIPAA risk assessment for these settings has to respect that reality. Templates written for a two-physician clinic miss half the building.

    What is different on the floor

    • Shared workstations and shared logins that fight unique user ID expectations
    • High vendor density: therapy platforms, pharmacy, labs, dietary, staffing agencies
    • Family and resident communications that wander into SMS and personal email
    • Medical devices and nurse call adjacent systems that IT does not fully own
    • Turnover that breaks training continuity every quarter

    Your risk analysis has to name those flows. If the document only discusses “the EHR,” it is describing a brochure, not the facility.

    Assessment focus areas that usually pay off

    1. ePHI inventory across clinical, billing, and communications tools
    2. Access provisioning and offboarding for employees and vendors
    3. Workstation and remote access patterns on the units
    4. Backup and downtime procedures when clinical systems fail
    5. BAAs and minimum necessary with the long vendor list
    6. Incident response that includes after-hours reality, not a daytime org chart

    Where Hestia fits (building, not claiming)

    Dark Edge is building Hestia as an internal direction for how we organize evidence and workflows around assessments in care settings like these. Treat that as product direction under construction, not a finished platform pitch and not a substitute for a human-led HIPAA risk assessment.

    Do not read this section as a case study. There are no customer results claimed here on purpose.

    Wording we will not use

    We will not call a facility certified, audited, validated, or compliant based on an assessment. Useful language is: completed a HIPAA risk assessment, produced a risk register, and is working a remediation plan. Framework alignment, where relevant: aligned with, management attestation available on request.

    Next step

    If you run rehab, skilled nursing, or assisted living and cannot hand someone a current risk analysis that matches your real systems, start there. We can scope a fixed-fee HIPAA risk assessment around the facility you actually operate.

  • A fixed-scope penetration test when the budget only has room for one serious look

    Budgets are tight. Plenty of owners are choosing between a serious security look and another tool that promises to “AI” the problem away. If you can fund one penetration test this year, scope it like a grown-up.

    This is not a shopping guide with prices. It is a way to spend scarce attention on the paths attackers actually use against small firms.

    What “fixed scope” should mean

    Agree in writing, before work starts:

    • In-scope hosts, apps, and identity tenants
    • Out-of-scope systems (and why)
    • Rules of engagement (hours, contacts, stop conditions)
    • Whether credentials are provided (authenticated vs black-box)
    • Deliverables: findings with severity, evidence, and a remediation order

    Open-ended “test everything” language is how you get a shallow sweep and a thick PDF.

    Prioritize paths that change business risk

    For most small offices, the high-value order looks like:

    1. External attack surface that should not exist (remote access, admin UIs, forgotten subdomains)
    2. Identity and cloud apps (Microsoft 365 / Entra, VPN, SSO apps) with an authenticated look when possible
    3. One critical internal path (file share ACL chaos, domain privilege paths, or the line-of-business app)

    If the budget only covers one of those deeply, pick identity-plus-external over a huge internal port scan that nobody will remediate.

    What to refuse

    • Unlimited retests sold as calm
    • “Guaranteed clean” language
    • Scope that quietly excludes the systems that hold customer or patient data
    • Reports that dump scanner output without human prioritization
    • Anything that requires you to brag about NDA bug-bounty theater in public marketing

    How to use the report afterward

    A pentest that sits in email is a sunk cost. Assign owners. Track closures. Re-test the critical findings. Feed the leftovers into your HIPAA risk assessment or general risk register so the next year is not amnesia.

    Dark Edge approach

    We favor fixed-scope engagements with clear rules and a remediation-first writeup. Findings are ordered by what is being exploited in the wild when that signal exists, not by which vulnerability makes the best screenshot.

    If you only have room for one serious look, make the scope match the business, not the sales deck.

  • Azure and HIPAA audit prep: what a practice under pressure should test first

    If a patient complaint, a breach notice, or a payer questionnaire just put HIPAA on your calendar, you do not need a 200-page binder. You need an order of work that matches how small practices actually run Microsoft 365 and Azure today.

    This is HIPAA audit preparation and HIPAA risk assessment work. It is not a promise that you are finished, “HIPAA ready,” or somehow cleared. Regulators care whether you know where ePHI lives and whether you can show decisions and evidence.

    Start with where ePHI actually is

    Before you open Azure Policy dashboards, list the systems:

    • Practice management / EHR
    • Imaging and sensor workstations
    • Microsoft 365 mail and OneDrive / SharePoint
    • Patient portals and fax/email gateways
    • Billing vendors and clearinghouses
    • Any Azure VM, storage account, or backup vault that holds exports

    If that inventory is fuzzy, stop decorating controls. Finish the inventory. OCR settlements keep citing missing or shallow risk analysis more than missing wallpaper policies.

    Then test identity, because identity is how breaches start

    For a Microsoft-heavy practice, the first technical pass should answer:

    1. Who has Global Admin or privileged roles, and is that standing access?
    2. Is MFA actually required on interactive admin and clinical staff paths, including break-glass handling?
    3. Are legacy authentication protocols still allowed?
    4. Which guest accounts and enterprise apps still have access?
    5. Are shared mailboxes interactive logins?

    Azure AD / Entra misconfiguration is not a side quest. It is the front door.

    Storage, backups, and logging next

    • Encryption settings on disks and storage that hold ePHI exports
    • Backup jobs that someone has restored on purpose in the last quarter
    • Log retention you can actually query (sign-in logs, audit logs, mailbox audit)
    • Conditional access gaps for apps that touch patient data

    A pretty Azure Security score with unrestorable backups is still a bad week waiting to happen.

    Policies and BAAs have to match the stack

    Auditors and investigators ask for documents that describe the environment you run, not a template from a blog. Business associate agreements should cover the vendors who can see ePHI. Workforce training should mention your real tools.

    Dark Edge wording for frameworks we align to: aligned with, management attestation available on request. We do not call this certified, audited, validated, or compliant.

    A sane two-week triage when pressure is high

    Week 1: ePHI inventory, Entra privileged access and MFA gaps, mailbox forwarding/rules sweep, confirm BAAs for top vendors.

    Week 2: backup restore drill on one critical system, patch and expose check on internet-facing hosts, draft or refresh the risk analysis outline with owners and dates.

    Then schedule the deeper HIPAA risk assessment so the triage notes become a durable record, not a panic folder.

    How Dark Edge helps

    We run HIPAA Security Risk Assessments for independent practices, with technical review of the Microsoft estate as part of that work. If we manage an environment, we do not assess that same environment. Independence matters when someone else is reading the report.

    Book a strategy call if you need a fixed-scope prep plan in writing before the calendar date lands.