locations · little rock

State agencies, a teaching hospital and a large bank all sit in Little Rock, and all of them get audited.

Arkansas runs its government from Little Rock, and UAMS and Bank OZK are based in the same city. Each keeps sensitive records about Arkansans and each gets audited. In our Little Rock conversations the question is how quickly they can show who had access, and why.

in short·20-second read

In Little Rock we work with state agencies and their contractors, academic and regional health systems, and banks.

The work covers identity governance and access reviews, privileged access for shared admin accounts, data platforms for clinical and agency reporting, and rules for AI tools on state and patient data. We are headquartered in Frisco, Texas, serve Arkansas clients remotely and travel to Little Rock for workshops and launches.

Cohash has no office in Arkansas. We are based in Frisco, Texas. Projects run remotely, and we travel in for discovery, design workshops and go-live weeks.

Ask an engineer facts checked 2026-10-21 · 8 sources
rules
Arkansas Personal Information Protection Act, Ark. Code §4-110-105Arkansas Act 1030 of 2019, biometric dataHIPAA Security Rule technical safeguards, 45 CFR §164.312
who and what

Who we work with in Little Rock, and the rules they work under

industries
  1. State agencies and their contractors

    Agency staff, county users and vendor developers often share one directory and a handful of admin accounts that nobody has rotated in years. We run access reviews by program, put shared admin accounts in a vault with session recording, and write the joiner and leaver rules so contractor access ends when the contract does.

  2. Academic medicine and hospitals

    A teaching hospital mixes clinicians, residents, students, researchers and regional clinic staff, and one person can hold three of those roles at once. We model those roles in the governance platform, connect them to the EHR and research systems and remove access when a rotation or study ends.

  3. Regional and community banking

    Banks that grew through acquisitions carry several cores, loan systems and branch directories. Examiners ask for evidence of least privilege and timely terminations. We consolidate entitlements, automate quarterly certifications and keep privileged access to the core under recorded sessions.

  4. AI use in government and health

    Arkansas already restricts some apps on state devices. Agencies and hospitals adding AI assistants still need a list of approved tools, an identity for each agent and rules on which records it can read. We help write that policy and build the controls that enforce it.

regulations
  1. Arkansas Personal Information Protection Act, Ark. Code §4-110-105 ↗

    If a breach affects more than 1,000 people, the Attorney General must be told at the same time as residents or within 45 days of determining a reasonable likelihood of harm, whichever is first. The written breach determination must be kept for five years and produced within 30 days of an AG request.

  2. Arkansas Act 1030 of 2019, biometric data ↗

    The same act added biometric data such as fingerprints, faceprints, retinal or iris scans, hand geometry and DNA to the definition of personal information when it is used to authenticate a person. Biometric sign-in data at hospitals or banks therefore falls under the breach law.

  3. HIPAA Security Rule technical safeguards, 45 CFR §164.312 ↗

    For academic and regional health systems and their vendors, the rule sets standards for access control, unique user IDs, audit controls, integrity and person or entity authentication on electronic PHI.

01Do we have to tell the Arkansas Attorney General about every breach?

No. AG notice applies when more than 1,000 people are affected, and the AG's office says it is required when you determine there is a reasonable likelihood of harm. Either way, keep the written determination for five years. Counsel should make the harm call.

02Does Arkansas have a comprehensive consumer privacy law like Texas?

We have not found one in force as of October 2026, so Arkansas obligations for most businesses come from the breach statute, sector rules such as HIPAA and GLBA, and contracts. If you also hold data on Texans or Tennesseans, those states' privacy acts may apply. Confirm with counsel.

03Our employees sign in with fingerprints on shared workstations. Is that covered?

Yes, if the fingerprint data authenticates them. Since Act 1030 of 2019 Arkansas counts biometric data used that way as personal information, so a leak of the template store is a reportable breach. We review where templates are stored and who can export them.

04How do you run access reviews for a state agency with many contractors?

We group access by program and system, assign each contractor account a sponsor and an end date, and send reviews to program managers who know the work. Accounts with no sponsor get disabled after a notice period you set.

sources 8 sources linked last checked 2026-10-21 content fingerprint 5ae2294e
  1. 01BLS, Little Rock-North Little Rock-Conway economy at a glancebls.gov ↗
  2. 02UAMS fast factsweb.uams.edu ↗
  3. 03Bank OZK, Aboutozk.com ↗
  4. 04Arkansas Department of Shared Administrative Services, Office of State Technologysas.arkansas.gov ↗
  5. 05Port of Little Rockportoflittlerock.com ↗
  6. 06Arkansas Act 1030 of 2019 (HB 1943), amending the Personal Information Protection Actarkleg.state.ar.us ↗
  7. 07Arkansas Attorney General, security or data breacharkansasag.gov ↗
  8. 0845 CFR §164.312 (Cornell LII)law.cornell.edu ↗
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