Attack surface visibility in Pittsburgh.

Why Pittsburgh organisations commission attack surface visibility

Pittsburgh is a major academic medical system paired with robotics, autonomy and advanced materials research. That economic profile decides what an attacker goes after here, and it should decide what a test is scoped to look for. A generic methodology applied without reference to the local industry mix produces a report full of findings nobody needed and silence on the ones that mattered.

What is specific to this market

Robotics and autonomy research sits alongside a major academic medical system, producing an unusual pairing: safety-critical embedded software on one side, protected health information at scale on the other. Pennsylvania imposes no comprehensive privacy statute and no AG notification duty, which means contractual and sectoral obligations, not state law, drive nearly all security requirements here.

Healthcare and health systems

Healthcare is the sector where a security failure becomes a clinical failure. Ransomware against a hospital does not merely encrypt files; it diverts ambulances and delays procedures. The pressure to restore service fast is precisely what makes healthcare a profitable target, and the sprawl of clinical devices, imaging systems and third-party portals gives an attacker unusually many ways in.

The HIPAA Security Rule requires periodic technical evaluation, and payers and health systems increasingly demand HITRUST or an equivalent third-party assessment before they will integrate a vendor.

Manufacturing and supply chain

Manufacturing combines high downtime cost with long-lived equipment and a deep supplier network, which is an unusually attractive combination. Ransomware operators price the ransom against a production line, and the same flat networks that make plant operations simple make lateral movement trivial once a foothold exists.

Supplier security audits have become a commercial gate — a customer questionnaire increasingly asks for evidence of independent testing, not a policy document.

Software and SaaS

For a software company the security boundary is the product itself. Multi-tenant isolation, authorisation logic, SSO and OAuth flows, webhook handlers and the CI/CD pipeline that ships all of it are where real findings live — and none of them are visible to a scanner that only checks for known CVEs. Broken object-level authorisation remains the single most common serious finding in modern application testing.

For most SaaS companies the pentest is not driven by regulation at all — it is driven by the enterprise deal that will not close without a current report and an attestation letter.

What Pennsylvania law expects of you

Security testing is not a compliance exercise, but in Pennsylvania the legal clock is what turns an unnoticed weakness into a reportable event with a deadline attached. Knowing the timeline in advance is what lets you decide how fast findings need to be remediated.

The practical consequence for Pittsburgh businesses is straightforward: a breach you discover on a Friday starts a clock that runs in calendar days, not business days. Testing exists to find the exposure before that clock ever starts — and to give you documented evidence of diligence if it does.

How the engagement runs

Attack surface visibility is the unglamorous foundation everything else sits on. Penetration tests scope to what you tell the tester about. Compliance evidence covers the systems you listed. Automated scanners only scan the targets in the queue. Every one of those activities inherits the blind spots of your inventory.

Secuur builds the inventory from the outside in — the same way an attacker would. We start from your domains and enumerate subdomains, resolve them, fingerprint what is listening, pull and parse every certificate, and attribute each asset back to a business owner. Then we keep doing it, because your surface changed while you were reading this.

1. Seed

You give us your domains — or just your primary one and we work outward from registration and certificate-transparency records.

2. Enumerate & grade

First full sweep completes in hours, not weeks. Every live TLS endpoint comes back with an A–F quantum grade attached.

3. Watch

Continuous re-discovery on your cadence. You get a diff, not another 400-row dashboard to go read.

Working with Pittsburgh teams

Engagements run remotely by default, which keeps scheduling simple and cost down. Where a scope genuinely needs physical presence — internal network testing from inside a facility, an operational technology environment, a physical access assessment — on-site time is planned into the statement of work rather than billed as a surprise. Reporting, walkthroughs and remediation support run on your calendar, not ours.

What the engagement covers

What these engagements typically surface

Discovery engagements rarely fail to find something. The consistent pattern is not that a team is careless — it is that infrastructure accumulates faster than any inventory process keeps up with, and nothing in the normal operating rhythm ever prompts a review.

Expired and misissued certificates

Certificates past expiry on hosts nobody monitors, wildcard certificates spread across far more systems than intended, and internal names leaked through certificate transparency logs that reveal naming conventions and unpublished environments.

Unintended administrative exposure

Management interfaces, database consoles, CI runners and monitoring dashboards reachable from the public internet, usually because a security group was widened during an incident and never narrowed again.

Third-party assets nobody owns

Marketing microsites, event registration pages and vendor-hosted portals operating under your domain with no security review, no patch cadence and no named internal owner.

None of the above is hypothetical or specific to Pittsburgh — these are the recurring patterns across engagements of this type. What varies by market is which of them carries the most consequence, and in Pittsburgh that is shaped by healthcare and health systems and manufacturing and supply chain exposure more than by anything else.

How to prepare

Bring a list of the domains you believe you own, including ones you have retired. The gap between that list and what discovery returns is itself the most useful output of a first engagement — and it is common for the delta to be the majority of the surface.

In Pittsburgh specifically, the framing that produces the most useful engagement follows from the local picture: robotics and autonomy research sits alongside a major academic medical system, producing an unusual pairing: safety-critical embedded software on one side, protected health information at scale on the other. Pennsylvania imposes no comprehensive privacy statute and no AG notification duty, which means contractual and sectoral obligations, not state law, drive nearly all security requirements here.. Scope the work against that, not against a generic checklist.

Define the question, not just the scope

The most valuable engagements start from a business question rather than an asset list. "Could an attacker reach our healthcare and health systems data from an ordinary employee laptop?" gives testers an objective and gives you a report you can act on. A scope that says only "test everything" produces breadth at the cost of the depth that actually changes decisions.

Fix the cheap findings first

If you already know a system is unpatched or a service is exposed, remediate it before testing begins. Paying senior testers to rediscover issues you have already identified spends the engagement budget on confirmation rather than discovery.

Agree the remediation path before the report lands

Decide in advance who receives findings, who assigns them, and what the target remediation window is by severity. In Pennsylvania this matters concretely: the breach-notification clock runs without unreasonable delay, so the difference between a finding fixed in a week and one that sits in a backlog for a quarter is the difference between a managed risk and a reportable event.

Plan for the retest

A finding is not closed until it has been verified closed. Build the retest into the engagement rather than treating it as a separate purchase, and keep the evidence — it is what an auditor, an enterprise customer or a cyber insurer will ask to see.

Compliance drivers that apply in Pittsburgh

These are the frameworks that most often make testing a requirement rather than a choice for organisations in this market. Which ones bind you depends on your sector, your customers and the data you hold.

• HIPAA Security Rule
• HITRUST CSF
• FDA premarket cybersecurity (device makers)
• SOC 2 Type II
• 42 CFR Part 2 (behavioural health)
• IEC 62443
• NIST CSF 2.0
• CMMC (defense supply chain)
• ISO/IEC 27001
• Customer supplier-security audits
• Customer security questionnaires
• GDPR (where EU data is processed)
• CSA STAR
• Pennsylvania breach notification — consumer notice without unreasonable delay

The layer nobody else tests

Conventional attack-surface tools tell you a host exists and what version it runs. They will not tell you that its TLS handshake negotiates a classical-only key exchange — which means every session it has ever served is harvestable today and readable the moment a cryptographically-relevant quantum computer exists.

Protected health information has a confidentiality horizon measured in a patient lifetime. A record encrypted today with classical key exchange and captured in transit is still sensitive in 2050 — which makes healthcare the clearest case for hybrid post-quantum TLS in front of clinical and patient-facing systems.

Every Secuur engagement grades each TLS endpoint in scope A–F on the key-exchange group it actually negotiates, using the same engine as our free readiness scan. Grade A means a hybrid post-quantum group such as X25519MLKEM768; a classical-only handshake grades D to F, because a session recorded today can be decrypted once a cryptographically relevant quantum computer exists. See the NIST post-quantum standards for the underlying algorithms, or the glossary for the terminology.

What you receive

• Full external asset inventory (CSV + JSON API)
• Per-endpoint A–F quantum-readiness grade
• Certificate register with key type, size and expiry
• Dangling-DNS and takeover-risk report
• Draft Cryptographic Bill of Materials (CBOM)
• Change diffs on your chosen cadence
• Per-endpoint A–F post-quantum readiness grade
• Attestation letter suitable for customers and auditors

Frequently asked questions

How is this different from a vulnerability scanner?

A vulnerability scanner tests targets you give it. Attack surface visibility discovers the targets in the first place. The two are complementary — discovery feeds the scanner its queue, which is why Secuur runs them together.

Do you need access to our infrastructure?

No. External discovery runs entirely from the outside using public DNS, certificate transparency logs and unauthenticated network probes — the same data any attacker can reach. Authenticated internal discovery is available as an add-on where you want cloud-account coverage.

What is a Cryptographic Bill of Materials?

A CBOM is an inventory of every cryptographic algorithm, key and certificate your systems depend on. It is the prerequisite for any post-quantum migration plan, and US federal guidance under NSM-10 and CNSA 2.0 increasingly expects agencies and their suppliers to maintain one.

How often does discovery run?

Weekly by default, daily or continuous on higher tiers. Certificate expiry and new-host events are alerted as soon as they are observed rather than waiting for the next full sweep.

Do you provide attack surface visibility in Pittsburgh?

Yes. Secuur serves Pittsburgh and the surrounding Pennsylvania market. Engagements run remotely by default, with on-site time scoped in where the work genuinely requires physical presence — internal network testing, operational technology environments or physical access assessments.

How quickly must we report a breach in Pennsylvania?

Pennsylvania requires consumer notification without unreasonable delay. No specific AG notification requirement; credit agencies at 1,000+. Those timelines run from discovery or determination, so the practical window to investigate and prepare notice is much shorter than the headline number suggests.

What does an engagement cost?

Scope drives price. A tightly scoped single-application or external test typically starts in the mid four figures; a multi-system engagement covering healthcare and health systems infrastructure runs materially higher. We scope from your actual estate — the free readiness scan is usually the fastest way to establish what that estate looks like.

Other services for Pittsburgh