locations · indianapolis

Drug makers, Medicaid plans and a cargo hub in Indy share one problem. Too many people see too much.

Indianapolis puts a global pharmaceutical headquarters, a diagnostics headquarters, the plans that run Indiana Medicaid and the second-biggest FedEx Express operation within a short drive of each other. Each one holds regulated data that a long list of contractors, researchers and partners need to touch.

in short·20-second read

For Indianapolis organizations we work on identity governance, privileged access and governed data platforms.

Life sciences teams need research and manufacturing data access that holds up to audit. Health plans serving Hoosier Healthwise, HIP and PathWays members need clean member identity and payer platform integration. Freight and logistics firms need frontline sign-in that works at 3 a.m. We work from Frisco, Texas, serve Indiana clients remotely and travel in for workshops and launches.

Cohash has no Indianapolis office. Our US base is Frisco, Texas, so Indiana work runs remotely, and we fly in for discovery sessions, design workshops and go-live support on site.

Ask an engineer facts checked 2026-10-21 · 12 sources
rules
Indiana breach disclosure, IC 24-4.9-3Indiana Consumer Data Protection Act, IC 24-15Indiana public-sector cyber incident reportingHIPAA Breach Notification Rule, 45 CFR 164.404
who and what

Who we work with in Indianapolis, and the rules they work under

industries
  1. Pharmaceuticals and diagnostics

    Research, clinical and manufacturing data sit in separate systems with separate owners, and contract research partners need access to slices of each. We set up role and attribute rules so a CRO analyst sees only their study, record every privileged change to validated systems, and build pipelines whose lineage an auditor can follow from instrument to report.

  2. Medicaid and commercial health plans

    A plan that serves Hoosier Healthwise, HIP and PathWays members juggles eligibility files from the state, provider rosters and broker portals. We fix duplicate member identities, wire the payer core to state feeds, and put provider and member portal sign-in on one customer identity platform.

  3. Air freight and distribution

    Sort centers and warehouses run on handhelds, shared terminals and seasonal hires who start the same week they are hired. We give those workers fast sign-in tied to a badge or device, cut access the day a contract ends, and keep partner carrier integrations on credentials that rotate on a schedule.

  4. State and local government

    Agencies in the capital are already moving users to app-based and FIDO MFA, and local units owe IN-ISAC a report within 48 hours of an incident. We help with phishing-resistant MFA rollouts, service account cleanup and the access logs that make a 48-hour report possible.

regulations
  1. Indiana breach disclosure, IC 24-4.9-3 ↗

    Since 1 July 2022 the owner of the data must notify affected Indiana residents and the Attorney General without unreasonable delay and no later than 45 days after discovering a breach. If more than 1,000 residents get notice, the nationwide consumer reporting agencies must be told as well.

  2. Indiana Consumer Data Protection Act, IC 24-15 ↗

    In effect from 1 January 2026 for businesses that process personal data of at least 100,000 Indiana residents a year, or 25,000 if more than half their revenue comes from selling data. The Attorney General enforces it, and the 30-day cure period has no sunset.

  3. Indiana public-sector cyber incident reporting ↗

    The state's cybersecurity hub tells local government and other public-sector entities to report ransomware, exploited vulnerabilities and denial-of-service attacks to IN-ISAC at the Indiana Office of Technology within 48 hours.

  4. HIPAA Breach Notification Rule, 45 CFR 164.404 ↗

    Covers the health plans and providers serving Indiana members. Affected individuals must be notified without unreasonable delay and no later than 60 calendar days after a breach is discovered.

01Does the Indiana Consumer Data Protection Act apply to a health plan?

That depends on the act's exemptions, which your counsel should read against your plan structure. What we can do is the groundwork. We map member claims data, marketing lists, website visitor data and broker leads to the systems that hold them, so counsel can decide which rule covers each set.

02We have 45 days to notify residents after a breach. How do we know who was affected?

You need to know which accounts touched which records, quickly. We set up identity logs and data access logs that can answer that for a given time window, so the 45-day clock is spent on notices instead of reconstruction.

03Can you work inside our GxP validated environment?

Yes, under your quality procedures. Access changes to validated systems go through your change control, and we document configuration and testing to the standard your validation team asks for. We do not issue validation sign-off ourselves.

04Our agency has to move off voice call MFA. What replaces it for field staff without smartphones?

FIDO security keys are the usual answer, and the state already lists them as an approved method. We plan the key inventory, enrollment days and a recovery process for lost keys so field staff are not locked out on day one.

05Do you help with AI use on clinical or research data?

We set the guardrails. That means deciding which data sets a model may read, logging prompts and outputs against named users, and keeping identifiable patient data out of tools that are not approved for it. The scientific review of the model stays with your teams.

next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it