locations · colorado springs

Space Force units, NORAD and their contractors share a city. Their access records must satisfy DoD assessors.

Work in Colorado Springs follows the bases. Contractors supporting Peterson, Schriever and the Academy handle controlled unclassified information, and the CMMC clauses now appearing in Defense contracts expect proof of who can reach it. Local cyber and software firms selling to those programs inherit it too.

in short·15-second read

Our Colorado Springs work centers on defense, space and cybersecurity contractors.

We set up identity and access controls that map to NIST SP 800-171 and CMMC, privileged access for engineering and ground-system environments, and lifecycle governance for staff who move between programs. Cohash works from Frisco, Texas, serves Colorado Springs remotely, and travels in for workshops and launches.

We don't have staff based in Colorado Springs. Cohash works from Frisco, Texas, runs engagements remotely, and sends people up for discovery, design workshops and cutovers.

Ask an engineer facts checked 2026-10-21 · 10 sources
rules
CMMC Program, 32 CFR Part 170DFARS CMMC contract clause ruleColorado breach notification, C.R.S. §6-1-716Colorado Privacy Act
who and what

Who we work with in Colorado Springs, and the rules they work under

industries
  1. Space operations and ground systems

    Satellite command and control, missile warning and mission networks depend on a small group of administrators and a long tail of vendor engineers. Shared admin accounts on ground-system servers are the pattern we see most. We give each person a named identity, route admin work through a PAM gateway with session recording, and expire vendor access when the support ticket closes.

  2. Defense primes and their subcontractors

    Plenty of firms here keep CUI in a separate enclave. The access model is where we put most of the effort. We define who belongs in the enclave, tie access to contract roles and training records, and generate the quarterly account reviews and audit logs an assessor will ask to see.

  3. Cybersecurity and software companies

    Security vendors and software shops selling to the programs around town carry two identity jobs. One is customer login for their own product, often for government tenants. The other is the build pipeline, where tokens and signing keys pile up. We handle both, with phishing-resistant MFA for customers and short-lived credentials in CI.

  4. Cleared and veteran workforce

    People here change programs, contracts and employers often, and each move should change what they can reach. Joiner, mover and leaver rules wired to HR and the security office keep a cleared engineer from carrying old program access into a new role.

regulations
  1. CMMC Program, 32 CFR Part 170 ↗

    Effective 16 December 2024. Sets three CMMC levels for contractors that handle federal contract information or CUI. Level 2 requires the 110 security requirements of NIST SP 800-171 Rev. 2, assessed by the contractor or by a certified third-party assessment organization depending on the contract.

  2. DFARS CMMC contract clause rule (2025) ↗

    Effective 10 November 2025, this rule puts CMMC requirements into Defense solicitations and contracts. For the first three years, program managers and requiring activities decide contract by contract whether to apply them, so requirements arrive unevenly across a supplier's work.

  3. Colorado breach notification, C.R.S. §6-1-716 ↗

    Businesses get 30 days from determining a breach to notify affected Colorado residents. A breach reasonably believed to affect 500 or more residents also goes to the Attorney General within those 30 days. Complying with a federal regulator's breach rules does not remove the Attorney General notice.

  4. Colorado Privacy Act ↗

    The Attorney General has enforced this act since 1 July 2023. It matters for firms here that also handle consumer data, since Colorado residents can ask to access, correct or delete it and can opt out of its sale.

01Can you get us ready for a CMMC Level 2 assessment?

We cover the identity-heavy parts. Access control, identification and authentication, and audit and accountability together hold 42 of the 110 NIST SP 800-171 requirements. We implement those controls and write up the evidence and system security plan sections for them. We are not a C3PAO and we don't certify anyone.

02Space Command headquarters is moving to Huntsville. Does that affect contractors here?

The Chamber & EDC still lists Combat Forces Command, Peterson, Schriever, NORAD and NORTHCOM in Colorado Springs, so much of the program work stays. Firms that support both cities end up with staff and systems in two states. That means one identity platform spanning two sets of facilities, plus Alabama's breach rules alongside Colorado's.

03How should we handle engineers who move between programs?

Treat a program change like a new hire for access purposes. Old program groups come off on the transfer date, new ones are requested and approved by the new program's owner, and the security office sees both changes. That one rule cleans up most of the access creep we find.

04We sell security software to Defense customers. Do you only work on internal IT?

No. We also build customer identity for products, including tenant separation and MFA that government customers will accept, and we clean up secrets and signing keys in build pipelines.

colorado

More cities in Colorado

All 82 cities
sources 10 sources linked last checked 2026-10-21 content fingerprint 7586472d
  1. 01BLS, Colorado Springs economy at a glancebls.gov ↗
  2. 02Colorado Springs Chamber & EDC, aerospace and defensecoloradospringschamberedc.com ↗
  3. 03Colorado Springs Chamber & EDC, Space Command transition and Golden Dome (October 2026)coloradospringschamberedc.com ↗
  4. 04Colorado Springs Chamber & EDC, cybersecurity and software developmentcoloradospringschamberedc.com ↗
  5. 05National Cybersecurity Centercyber-center.org ↗
  6. 06US Air Force Academy, aboutusafa.edu ↗
  7. 07Federal Register, CMMC Program final rule (32 CFR Part 170)federalregister.gov ↗
  8. 08Federal Register, DFARS CMMC final rulefederalregister.gov ↗
  9. 09Colorado Attorney General, data protection laws and breach reportingcoag.gov ↗
  10. 10Colorado Attorney General, Colorado Privacy Actcoag.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