locations · fort worth

Fighter jets, freight trains and an airline operations center all run on accounts that someone has to govern.

Fort Worth builds military aircraft and helicopters, is home to BNSF's headquarters and American Airlines' campus. Suppliers to the plants face CMMC deadlines, and the railroad answers to TSA cyber directives. All of them run large shift-based workforces.

in short·15-second read

In Fort Worth, Cohash works with aerospace and defense suppliers, railroads and logistics operators, airlines and financial services firms.

For defense suppliers that means CUI enclaves, MFA and access evidence for CMMC. Rail and cargo operators get privileged access for operational systems and identity for frontline crews. We're based in Frisco, Texas, serve Fort Worth remotely and drive over for workshops, cutovers and launches.

Cohash's US office is in Frisco, about an hour from downtown Fort Worth, and we have none in Fort Worth itself. Build work is remote, and we come to your plant, yard or campus for discovery, workshops and go-live.

Ask an engineer facts checked 2026-10-21 · 10 sources
rules
Tex. Bus. & Com. Code §521.053, breach noticeTexas Data Privacy and Security Act, Bus. & Com. Code ch. 541CMMCTSA rail cybersecurity directives
who and what

Who we work with in Fort Worth, and the rules they work under

industries
  1. Aerospace and defense suppliers

    Machine shops, avionics firms and engineering subcontractors in the prime contractors' supply chains hold drawings and specifications marked as CUI, sometimes export-controlled too. Engineers share CAD workstations and vendor portals. We separate those workloads into an enclave with its own identities, require phishing-resistant MFA, and record who opened what, so CMMC evidence comes from logs.

  2. Freight rail and intermodal

    A railroad's dispatch, signaling and yard systems sit behind service accounts and vendor connections that predate the TSA directives. Train crews, mechanics and contractors also need mobile access in the field. We put operational access behind a PAM gateway, rotate the machine credentials, and give field staff sign-in that works on rugged devices and spotty coverage.

  3. Airlines and air cargo

    Airline headquarters and cargo hubs combine crew scheduling, maintenance records and partner booking systems, with alliance partners and ground handlers needing narrow slices of each. We design partner federation and API authorization so a handler sees its own flights and nothing more, and clean up the shared kiosk and tablet logins in hangars and on ramps.

  4. Brokerage and financial operations

    Brokerage and asset-management campuses in Westlake and north Fort Worth run large client-service floors. The work there is customer identity for investors, entitlement reviews for advisors and operations staff, and data pipelines that keep client records consistent between the CRM and the books of record.

regulations
  1. Tex. Bus. & Com. Code §521.053, breach notice ↗

    Notice to each affected individual is due no later than the 60th day after you determine a breach. Breaches touching 250 or more Texas residents also require an electronic report to the Attorney General within 30 days, including the number of Texans affected and whether police are investigating.

  2. Texas Data Privacy and Security Act, Bus. & Com. Code ch. 541 ↗

    In force since 1 July 2024. Consumers can name an agent to opt out on their behalf through a browser setting or a global device setting, so your consent stack has to honor those signals. The Attorney General alone enforces the law.

  3. CMMC (32 CFR 170 and the DFARS clause) ↗

    Phase 1 began with the DFARS rule on 10 November 2025, requiring self-assessed Level 1 or Level 2 status where a solicitation calls for it. Phase 2, which would have added third-party Level 2 certification from 10 November 2026, was suspended on 13 July 2026 pending a review. An award can be blocked if your SPRS status falls short.

  4. TSA rail cybersecurity directives (SD 1580 series) ↗

    TSA reissued SD 1580-21-01, Enhancing Rail Cybersecurity, as version E on 15 January 2026, and SD 1580/82-2022-01, Rail Cybersecurity Mitigation Actions and Testing, as version E on 1 May 2026. Designated railroads should read the current versions for access control and testing duties.

01We're a tier-two supplier to a prime. Will our CMMC level come from the prime or from DoD?

The level is set in the solicitation and flows down through the prime's subcontract, based on whether you'll handle FCI only or CUI. Ask your prime which level your work package carries. If it's Level 2, note that the C3PAO certification step planned for November 2026 is suspended pending a review, so for now the requirement is a self-assessment.

02Can offshore engineers work on our defense program?

That's a question for your export compliance officer and your contract terms before it's one for us. Cohash has offices outside the US, so we agree in the statement of work which tasks and data stay with US-based staff, and set up access so the enclave enforces that split.

03Our yard and shop staff share tablets. Is individual sign-in realistic?

Yes, if it takes seconds. Badge tap, a FIDO2 key on a lanyard or a short PIN with device trust usually works. We test with actual crews at shift change before rollout, because that's when shared logins come back.

04Do the TSA rail directives cover every railroad?

No. They apply to the freight and passenger railroads TSA designates, and the directive text sets the scope. Short lines and contractors outside that list may still see the requirements through their contracts with a designated railroad.

05Does the Texas privacy act require us to honor browser opt-out signals?

Chapter 541 lets consumers opt out through an authorized agent using a browser setting, extension or global device setting, and it can't be a default. Your consent platform needs to read those signals on sites and apps aimed at Texans. Confirm details with counsel.

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