locations · charleston

Charleston builds jets, ships cars and writes Navy software. Each has its own idea of a trusted account.

Around Charleston harbor sit a widebody jet line, vehicle plants and their suppliers, container terminals on the Cooper and Wando rivers, and a Navy information warfare center ringed by contractors. Their identity problems differ, but most trace back to suppliers and vendors with standing access.

in short·15-second read

Cohash helps Charleston-area defense IT contractors, aerospace and automotive suppliers, port operators and health systems manage access.

Contractors need CMMC-aligned identity controls around CUI. Plants and terminals need vendor remote access that is brokered, recorded and protected with MFA under Coast Guard and customer requirements. We're headquartered in Frisco, Texas, serve the Lowcountry remotely and travel in for workshops and launches.

Cohash has no Charleston office. Work is run from Frisco, Texas and delivered remotely, and we travel to the Lowcountry for discovery workshops, plant or terminal walk-throughs and cutovers.

Ask an engineer facts checked 2026-10-21 · 10 sources
rules
South Carolina breach notification, S.C. Code §39-1-90CMMC Program and DFARS clauseCoast Guard maritime cybersecurity, 33 CFR Part 101 Subpart FHIPAA Security Rule
who and what

Who we work with in Charleston, South Carolina, and the rules they work under

industries
  1. Defense IT and naval contractors

    Firms supporting Navy information warfare programs handle CUI daily and often run several contracts in one network. We design the CUI enclave identity model, separate administrative accounts from daily ones, add phishing-resistant MFA, and gather the evidence a CMMC Level 2 assessment expects for access control and identification.

  2. Aerospace and automotive manufacturing

    Large assembly plants and their tier-one suppliers trade engineering data and grant each other remote access to production systems. We put supplier engineers into a federated or brokered access path with an expiry, keep plant-floor systems off shared credentials, and log every vendor session.

  3. Container terminals and logistics

    Cranes, gates and yard systems depend on vendors who support them remotely. Under the Coast Guard's 2025 rule, regulated facilities need MFA on remotely reachable OT and separate credentials on critical systems. We inventory vendor paths and replace standing access with approved, time-limited sessions.

  4. Academic health and hospitals

    A statewide academic health system mixes clinicians, students, researchers and affiliates on one network. We tie access to role and appointment dates, keep research data access scoped to approved studies, and help privacy teams answer who viewed a record and why.

regulations
  1. South Carolina breach notification, S.C. Code §39-1-90 ↗

    Residents get notice in the most expedient time possible when illegal use has occurred, is reasonably likely, or creates a material risk of harm. A business holding someone else's data tells the owner immediately. Notices to more than 1,000 people go to the Department of Consumer Affairs and the credit bureaus.

  2. CMMC Program and DFARS clause ↗

    DoD began putting CMMC requirements into solicitations on 10 November 2025, starting with Level 1 and Level 2 self-assessments, which remain in place. Phase 2, which would have added third-party certification for applicable Level 2 contracts from 10 November 2026, was suspended on 13 July 2026 pending a review.

  3. Coast Guard maritime cybersecurity, 33 CFR Part 101 Subpart F ↗

    Facilities regulated under 33 CFR Part 105 need a Cybersecurity Officer, a Cybersecurity Plan and account controls including MFA, least privilege and separate credentials for critical IT and OT. Reportable cyber incidents go to the National Response Center.

  4. HIPAA Security Rule ↗

    Hospitals and health plans protect electronic PHI with access controls, audit logs and authentication of each user or system, and business associates such as billing or analytics vendors carry the same duties for the data they handle.

01We're a small contractor supporting a Navy program. Is CMMC Level 2 realistic for us?

Yes, especially if CUI stays inside a small, well-defined enclave. Many small firms use a cloud environment built for CUI and focus their effort on identity, MFA, logging and documentation. We scope the boundary first, because a smaller boundary means fewer controls to prove.

02A supplier needs remote access to our production line. What's the safe pattern?

Named accounts for each supplier engineer, access requested per job and approved by your plant team, a broker or jump host that records the session, and automatic expiry. No shared vendor password and no always-on VPN tunnel.

03Does South Carolina have a fixed breach notice deadline?

No day count. Section 39-1-90 asks for the most expedient time possible and without unreasonable delay, with an allowance for law enforcement holds. Federal rules may set firmer clocks, such as HIPAA's 60-day outer limit or DoD's 72-hour incident reporting for defense contractors.

04Do you work on OT networks directly?

We work on the identity and access layer around them, such as jump hosts, vendor access and account controls, and coordinate with your OT engineers and control system vendors on anything that touches the process network itself.

sources 10 sources linked last checked 2026-10-21 content fingerprint d7f1b191
  1. 01Department of War, CMMC Phase II requirements suspended (July 2026)business.defense.gov ↗
  2. 02Charleston Regional Development Alliancecrda.org ↗
  3. 03SC Ports, aboutscspa.com ↗
  4. 04MUSC, aboutmusc.edu ↗
  5. 05BLS, Charleston-North Charleston-Summerville economy at a glancebls.gov ↗
  6. 06S.C. Code Title 39 Chapter 1 (§39-1-90)scstatehouse.gov ↗
  7. 07Federal Register, CMMC program rulefederalregister.gov ↗
  8. 08Federal Register, DFARS CMMC acquisition rulefederalregister.gov ↗
  9. 09eCFR, 33 CFR Part 101 Subpart Fecfr.gov ↗
  10. 10HHS, HIPAA Security Rulehhs.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