locations · tulsa

Tulsa runs gas pipelines and rebuilds jet engines. Both jobs depend on vendors reaching into live systems.

Two major midstream companies keep their head offices downtown, and American Airlines runs a huge maintenance base by the airport. The shared problem is outside access. Contractors, OEM field engineers and integrators need a way into control systems and shop-floor networks that someone can audit afterward.

in short·15-second read

In Tulsa our work is mostly for midstream energy operators, aviation maintenance and aerospace manufacturers, and the city's growing tech employers.

We broker vendor access to pipeline control networks, put rotation and owners on service accounts, and build data pipelines from historians and maintenance systems into analytics platforms. We serve Tulsa remotely from our Frisco, Texas office and travel up for workshops, cutovers and launches.

We have no Tulsa office. Engineers work from our Frisco, Texas headquarters and travel to control centers, hangars and plants for discovery, design workshops and cutover weekends, then support the rollout remotely.

Ask an engineer facts checked 2026-10-21 · 10 sources
rules
Oklahoma breach notice law, 24 O.S. §163Oklahoma Consumer Data Privacy Act, 75A O.S.TSA Security Directive Pipeline-2021-02 series
who and what

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

industries
  1. Midstream pipelines and gas processing

    Gathering systems, processing plants and long-haul lines are run from control centers that integrators and compressor vendors need to reach. Those paths often go through a shared VPN account and a jump box no one has rebuilt in years. We map each route into the OT network, retire the shared ones and put the rest behind a vault with recorded, time-boxed sessions.

  2. Aircraft maintenance and aerospace manufacturing

    MRO hangars and engine shops carry thousands of technicians on shared terminals, plus OEM portals, parts suppliers and FAA records systems. We give technicians fast badge or PIN sign-in on shop-floor devices, keep their identities in step with HR and union rosters, and separate supplier portal accounts from the internal network.

  3. Remote-first and software employers

    Companies hiring through the local tech pipeline tend to start with one cloud tenant and a handful of admins who hold everything. We split admin roles, add phishing-resistant MFA and set up joiner and leaver flows before the headcount doubles.

regulations
  1. Oklahoma breach notice law, 24 O.S. §163 (as amended by SB 626) ↗

    From 1 January 2026, a breach affecting at least 500 Oklahoma residents (1,000 for a credit bureau) must also be reported to the Attorney General, no later than 60 days after residents are told. The report covers dates, data types, the count and the safeguards in place.

  2. Oklahoma Consumer Data Privacy Act, 75A O.S. (SB 546) ↗

    Starts 1 January 2027. A business processing personal data of 100,000 or more Oklahomans a year must honor access, correction, deletion and opt-out requests within 45 days and run data protection assessments for targeted advertising and sensitive data. Only the Attorney General enforces it.

  3. TSA Security Directive Pipeline-2021-02 series ↗

    For pipeline owners TSA has designated, it requires an approved Cybersecurity Implementation Plan with network segmentation, access control for critical cyber systems, continuous monitoring and an annual assessment program. Gas gathering and transmission companies headquartered in Tulsa may fall in scope.

01How do you handle compressor and SCADA vendors who need remote access to our control network?

We give each vendor a named account that only works through a brokered gateway, needs approval for a time window and records the session. Shared VPN logins go away. Your OT engineers keep a separate path with tighter rules, and nothing reaches field devices directly from the corporate network.

02Do we have to tell the Oklahoma Attorney General about every breach?

No. Since 1 January 2026 the AG notice applies when a single breach affects 500 or more Oklahoma residents, and it is due within 60 days after you notify those residents. Smaller breaches still need resident notice. Ask counsel how federal rules you follow interact with it.

03Can MRO technicians use passwordless sign-in on shared hangar terminals?

Usually, through a badge tap or a short PIN tied to the device, so a technician switching between work cards does not retype a password. The choice depends on your terminal hardware and on how the maintenance records system handles electronic signatures, which we check first.

04Our historian data is going to a cloud warehouse. Who should be able to read it?

Fewer people than you'd guess. We scope access by asset, region and use case, give the extraction job its own rotated credential, and keep a record of which reports drew on which tags.

05Is the Oklahoma privacy law in force yet?

Not until 1 January 2027. If you process data on 100,000 or more Oklahoma consumers, use the time to set up a rights-request process and data inventory. Employee and B2B contact data are outside its scope.

sources 10 sources linked last checked 2026-10-21 content fingerprint c1f4d3c1
  1. 01Williams, contact pagewilliams.com ↗
  2. 02Williams homepage (pipeline footprint)williams.com ↗
  3. 03ONEOK, About Usoneok.com ↗
  4. 04Oklahoma Department of Commerce, American Airlines Tulsa jobs (September 2024)okcommerce.gov ↗
  5. 05BLS, Tulsa economy at a glancebls.gov ↗
  6. 06Tulsa Remote, 2025 economic impact reportblog.tulsaremote.com ↗
  7. 07GovInfoSecurity, Tulsa ransomware attackers leaked 18,000 files (June 2021)govinfosecurity.com ↗
  8. 08Oklahoma SB 626, enrolled textoklegislature.gov ↗
  9. 09Oklahoma SB 546, enrolled textoklegislature.gov ↗
  10. 10TSA security directives and emergency amendmentstsa.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