locations · boise

Fab construction crews and rural clinic networks both test how fast Boise can grant and revoke access.

Micron started in a Boise dental office basement in 1978 and is now growing its home campus. St. Luke's, founded in 1902, runs hospitals and clinics out of the same valley. The questions we hear in Boise are about speed. How quickly can a contractor or clinician get in, and does their access end the day they leave?

in short·15-second read

For Boise organizations we handle workforce and contractor identity, privileged access to manufacturing and utility systems, and data pipelines for health systems.

Semiconductor suppliers need quick onboarding for construction and tool vendors, with clean offboarding afterwards. Health providers need access tied to credentialing. We serve Idaho remotely from our Frisco, Texas headquarters and travel to Boise for workshops and launches.

Cohash has no office in Idaho. Our US base is Frisco, Texas, and we run Boise engagements remotely, flying in for discovery sessions, design workshops and go-live support.

Ask an engineer facts checked 2026-10-21 · 7 sources
rules
Idaho breach notification, Idaho Code §28-51-105HIPAA Security Rule, 45 CFR Part 164 Subpart C
who and what

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

industries
  1. Semiconductor manufacturing and its suppliers

    A fab expansion brings in general contractors, tool vendors and field service engineers, each needing badges, network access and sometimes remote sessions into equipment. We give every outside worker a named sponsor and an end date at creation, route vendor sessions to process tools through a recorded gateway, and track the service accounts that move data between tools and manufacturing systems.

  2. Hospitals, clinics and health plans

    Systems in the Treasure Valley staff clinics across a wide rural area, and the same nurse may work three sites in a month. Access should follow the shift assignment from scheduling and credentialing, with break-glass access to charts logged and reviewed. Where a provider also runs a health plan, we keep member and patient data roles apart.

  3. Hydro and utility operations

    Remote dams and substations often rely on a handful of shared vendor logins kept on a spreadsheet. We vault those credentials, put each remote session behind approval and recording, and separate corporate identities from the operations network so a phished office account cannot reach control systems.

  4. State agencies in the capital

    Idaho agencies have 24 hours to tell the attorney general about a breach. Meeting that clock depends on knowing which accounts touched the affected system. We centralize sign-in and privileged session logs so an agency can answer that in an afternoon.

regulations
  1. Idaho breach notification, Idaho Code §28-51-105 ↗

    After a prompt good-faith investigation, entities notify affected Idaho residents without unreasonable delay when misuse has occurred or is reasonably likely. Public agencies must notify the attorney general within 24 hours of discovery, and anyone holding data for another party must tell the owner immediately.

  2. HIPAA Security Rule, 45 CFR Part 164 Subpart C ↗

    Applies to Idaho hospitals, clinics and health plans that handle electronic protected health information. The technical safeguards call for unique user identification, emergency access procedures, audit controls and person or entity authentication.

01Does Idaho have a consumer privacy act like Colorado or Utah?

Not a comprehensive one as of October 2026. For most Idaho businesses the main state data law is the breach notification chapter in Title 28. If you sell to people in states that do have privacy acts, those rules can still reach you, so start by mapping where your customers live.

02We bring in large contractor crews during a tool install. How do we stop their access lingering?

Tie every contractor account to a sponsor and a hard end date when it is created, and let it expire on its own. Badge, VPN and application access should hang off that one record. A weekly report of accounts past their end date catches anything the automation missed.

03Can equipment vendors keep remote access to our process tools?

Yes, through a gateway that asks for approval per session and records it, instead of a standing VPN account. That keeps the support terms in your tool contracts intact while giving you a log of who connected, when and to which machine.

04Our clinicians move between rural sites. How should their access follow them?

Drive it from the scheduling or credentialing feed. When a nurse is assigned to a clinic, the roles for that location turn on, and they turn off when the assignment ends. Copying a colleague's access, the usual shortcut, is where excess permissions pile up.

05We're an Idaho agency. What does the 24-hour rule mean for identity logs?

You need sign-in, privileged session and directory change logs in one place, kept long enough to cover how long an attacker might sit unnoticed. With that, telling the attorney general what happened within a day becomes realistic.

sources 7 sources linked last checked 2026-10-21 content fingerprint 05ea037e
  1. 01Micron, about the companymicron.com ↗
  2. 02Boise Valley Economic Partnershipbvep.org ↗
  3. 03BLS, Boise City-Nampa economy at a glancebls.gov ↗
  4. 04St. Luke's Health System, aboutstlukesonline.org ↗
  5. 05Idaho Power, company informationidahopower.com ↗
  6. 06Idaho Code §28-51-105legislature.idaho.gov ↗
  7. 07eCFR, 45 CFR Part 164 Subpart Cecfr.gov ↗
Reviewed by the Cohash team Product names are trademarks of their owners. how we handle facts and data →
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