locations · sioux falls

Card servicing floors, two large health systems and a food plant. Each has its own way to lose an account.

In Sioux Falls a single employer list covers card issuers, two regional health systems and a Smithfield Foods plant. Card servicing puts large agent teams in front of account data, hospitals have clinicians spread across rural clinics, and a processing line has shared consoles that cannot pause for a login.

in short·20-second read

In Sioux Falls we work with card issuers and banks, health systems and food processors on identity governance, privileged access, customer sign-in and the data platforms behind them.

For banks that means access reviews that examiners recognize and evidence for incident reporting. For hospitals and plants it means clinician and contractor lifecycle control. We are based in Frisco, Texas, work with South Dakota teams remotely and travel to Sioux Falls for workshops and launches.

We do not have a Sioux Falls office. Cohash works with South Dakota organizations remotely from Frisco, Texas, and travels in for discovery, design workshops, plant or hospital walk-throughs and go-live support.

Ask an engineer facts checked 2026-10-21 · 9 sources
rules
South Dakota breach notification, SDCL 22-40-19 to 22-40-26Computer-Security Incident Notification RuleSouth Dakota SB 49 , genetic data privacy
who and what

Who we work with in Sioux Falls, and the rules they work under

industries
  1. Credit card issuing and consumer banking

    Card servicing and collections centers run large agent populations with access to account and payment data, plus vendors for statements, fraud scoring and dispute handling. We tie agent entitlements to role and queue, record privileged sessions on servicing platforms, and put owners and rotation on the machine credentials that move data to processors.

  2. Regional health systems

    Health systems based in Sioux Falls staff hospitals, rural clinics and senior care sites across a wide rural region, so clinicians and traveling staff often carry accounts in more than one EHR domain. We build lifecycle rules from credentialing and HR feeds and keep HIPAA access reviews current without manual exports.

  3. Food processing and manufacturing

    Processing plants run refrigeration, packaging and line controls that maintenance contractors and equipment vendors reach remotely. We route that access through a brokered, recorded gateway with time limits and keep plant-floor operator logins simple, since a stalled sign-in on a line console is a safety and food-safety problem.

regulations
  1. South Dakota breach notification, SDCL 22-40-19 to 22-40-26 ↗

    Notify affected residents within 60 days of discovery. Breaches of more than 250 residents also go to the Attorney General, and consumer reporting agencies must be told without unreasonable delay. The Attorney General may seek up to $10,000 per day per violation.

  2. Computer-Security Incident Notification Rule (OCC, Federal Reserve, FDIC) ↗

    Banking organizations notify their primary federal regulator no later than 36 hours after determining a notification incident occurred. Bank service providers alert customers after disruptions of four or more hours. Full compliance applied from 1 May 2022.

  3. South Dakota SB 49 (2026), genetic data privacy ↗

    Signed 23 March 2026 and effective 1 July 2026. Covers direct-to-consumer genetic testing companies with consent, security and deletion duties, enforced by the Attorney General. South Dakota has no comprehensive consumer privacy law.

01Does South Dakota have a privacy law like Iowa's?

Not a comprehensive one. South Dakota relies on its breach notification statute and narrower laws such as the 2026 genetic data act. A Sioux Falls company with customers in neighboring states may still fall under those states' privacy laws, so map where your customers live.

02When can we skip notifying residents after a breach?

Only after an appropriate investigation and notice to the Attorney General, if you reasonably decide the breach will not likely harm anyone. You must document that decision in writing and keep it at least three years. Talk to counsel before relying on it.

03Our card servicing center has thousands of agents. Where should access cleanup start?

With the servicing and collections platforms, because that is where account data is broadest. We group agents by queue and function, remove standing access to bulk export, and put supervisors and admins behind recorded sessions. Quarterly reviews then cover far fewer exceptions.

04Can you help a health system with clinicians who work across many sites?

Yes. We make one identity per clinician the source of truth, driven by credentialing, and grant EHR and clinic-system access from it by site and role. When privileges end at one facility, only that access is removed.

05What about remote vendor access to a processing plant?

We put equipment vendors and contractors on a brokered gateway with approval, time limits and session recording, separate from your engineers' path. Line consoles keep local, physical access controls so production never waits on an MFA prompt.

sources 9 sources linked last checked 2026-10-21 content fingerprint d0b79435
  1. 01BLS, Sioux Falls economy at a glancebls.gov ↗
  2. 02Sioux Falls Development Foundation, major employers (June 2026)siouxfallsdevelopment.com ↗
  3. 03SDPB, When Citibank came to South Dakota (2015)sdpb.org ↗
  4. 04SDCL 22-40-20, notice of breachsdlegislature.gov ↗
  5. 05SDCL 22-40-24, notice to consumer reporting agenciessdlegislature.gov ↗
  6. 06SDCL 22-40-25, enforcementsdlegislature.gov ↗
  7. 07FDIC FIL-74-2021, computer-security incident notificationfdic.gov ↗
  8. 08South Dakota Legislature, 2026 SB 49sdlegislature.gov ↗
  9. 09Hunton, South Dakota enacts genetic data privacy acthunton.com ↗
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