locations · bridgeport

A card issuer with 70.7 million active accounts in Stamford and a helicopter program in Stratford.

Fairfield County puts two very different security problems close together. In Stamford, Synchrony's attack surface is millions of consumer logins and retail partner APIs. In Stratford, a principal Sikorsky site, the question is who can open a controlled drawing.

in short·15-second read

Around Bridgeport and Stamford we work with consumer finance companies, defense manufacturers and their suppliers, and hospitals.

For lenders the focus is customer identity, account takeover defenses and partner API credentials. For the helicopter supply chain it is access control over controlled unclassified information ahead of CMMC assessments. Cohash operates from Frisco, Texas, serves Fairfield County remotely and comes in for workshops and launches.

There is no Cohash office in Connecticut. We run Fairfield County projects remotely from Frisco, Texas, and send consultants to Bridgeport, Stamford or Stratford for kickoff workshops, assessment prep and go-live support.

Ask an engineer facts checked 2026-10-21 · 9 sources
rules
Connecticut breach notice, C.G.S. §36a-701bConnecticut Data Privacy Act as amended by Public Act 25-113DFARS CMMC clause
who and what

Who we work with in Bridgeport, and the rules they work under

industries
  1. Card issuing and consumer lending

    Private label and co-brand programs run sign-in, applications and servicing across the issuer's own apps and its retail partners' checkout flows. Account takeover, synthetic identities and credential stuffing all land here first. We design customer identity with risk-based step-up, passkeys where partners can support them, and short-lived tokens for partner APIs, plus the fraud signals that feed decision models.

  2. Helicopter manufacturing and its supply base

    Prime contractor programs push CMMC clauses down to machine shops, composites suppliers and engineering firms, many of them small. Their controlled technical data often sits in shared drives and email. We scope an enclave, move CUI into it, put multifactor sign-in on every path in and keep the access records an assessor will ask for.

  3. Community and teaching hospitals

    Hospitals in a multi-campus system share an EHR and a workforce, but each campus has its own badge readers, devices and local applications. Float nurses and residents cross between them weekly. We align role-based access across campuses, add fast badge sign-in on shared clinical workstations and review who can open records outside their unit.

regulations
  1. Connecticut breach notice, C.G.S. §36a-701b ↗

    The 60-day outer limit for notifying Connecticut residents runs from discovery. Notice to the Attorney General goes out no later than resident notice, and exposure of a Social Security number triggers an offer of at least 24 months of identity theft prevention services at no cost.

  2. Connecticut Data Privacy Act as amended by Public Act 25-113 ↗

    Since 1 July 2026 the CTDPA reaches controllers handling personal data of 35,000 or more Connecticut consumers, and any controller that processes sensitive data or sells personal data, regardless of volume. Consumers can also ask for the list of third parties their data was sold to.

  3. DFARS CMMC clause (48 CFR, DFARS Case 2019-D041) ↗

    Effective 10 November 2025, this rule lets contracting officers require a current CMMC status as a condition of award and requires primes to flow the requirement down to subcontractors that handle FCI or CUI. Phase 1 self-assessments apply now, and the Phase 2 certification step was suspended on 13 July 2026 pending a review.

01We machine parts for a helicopter program. How small can our CMMC scope be?

Often much smaller than the whole company. If controlled drawings and specs live only in a separate enclave, such as a dedicated cloud tenant, the assessment can focus on that enclave and the people who use it. The work is moving the data there and proving it doesn't leak back to email and shop floor PCs.

02Do the 2026 CTDPA amendments matter if we only have a few thousand Connecticut customers?

They can. Processing any sensitive data, such as health, biometric or precise location data, now brings a controller in scope regardless of volume. A small retailer or app developer should check what it collects before assuming it falls below the line. HIPAA covered entities and certain banks are exempt, so hospitals answer to HIPAA instead.

03How do you cut account takeover without hurting card activation?

By putting friction only where risk is. Device binding, passkeys and behavioral signals let most sign-ins pass quietly, and step-up checks go to the sessions that look wrong. We tune those rules against your fraud losses and call center volume, not a vendor default.

04Can hospital staff use badge tap-in on shared workstations?

Yes, and it is usually the most popular change we make. Clinicians tap a badge to open a shared session and tap again to leave, with a PIN or biometric at set intervals. We check it against your EHR vendor's supported options first.

connecticut

More cities in Connecticut

All 82 cities
sources 9 sources linked last checked 2026-10-21 content fingerprint 8283bfee
  1. 01Department of War, CMMC Phase II requirements suspended (July 2026)business.defense.gov ↗
  2. 02BLS, Bridgeport-Stamford-Danbury economy at a glancebls.gov ↗
  3. 03Synchrony Financial, 2025 Form 10-Ksec.gov ↗
  4. 04Lockheed Martin, 2025 Form 10-Ksec.gov ↗
  5. 05Bridgeport Hospital, aboutbridgeporthospital.org ↗
  6. 06Connecticut General Statutes chapter 669 (§36a-701b)cga.ct.gov ↗
  7. 07Connecticut Public Act 25-113 (SB 1295)cga.ct.gov ↗
  8. 08Foley & Lardner, CTDPA amendments (July 2026)foley.com ↗
  9. 09Federal Register, DFARS CMMC rulefederalregister.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