Attack surface visibility in San Jose.

Why San Jose organisations commission attack surface visibility

San Jose is the core of Silicon Valley, where the product itself is the security boundary for most of the local economy. 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

In Silicon Valley the product is the perimeter. Companies here are typically strong on infrastructure hygiene and weak on authorisation logic, because the former is automated and the latter is application-specific. The findings that matter are cross-tenant access and business-logic abuse, and they are only reachable by a tester given credentials in two separate tenants and time to understand the domain model.

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.

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.

Aerospace and advanced engineering

Aerospace programmes combine export-controlled technical data, a deep supplier tier and safety-critical embedded systems on multi-decade service lives. The realistic threat is a patient actor inside a supplier network, and the consequences of a compromised design artefact are measured in programme years, not incident hours.

Export-control obligations shape the engagement itself — tester nationality, data residency and evidence handling all become scoping constraints before methodology is discussed.

What California law expects of you

Security testing is not a compliance exercise, but in California 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.

CPPA risk-assessment regulations phase in from April 2028, and the Delete Act imposes data-broker deletion duties.

The practical consequence for San Jose 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 San Jose 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.

Forgotten staging and pre-production hosts

Environments stood up for a launch and never decommissioned, frequently running an older application build with debug endpoints enabled and no WAF in front of them. They hold real data more often than teams expect.

Dangling DNS records

A CNAME still pointing at a deprovisioned cloud bucket, app platform or CDN property. Anyone who registers that resource name inherits your subdomain, which is enough to serve content from your origin, take cookies scoped to the parent domain, or pass domain-validated certificate issuance.

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.

None of the above is hypothetical or specific to San Jose — these are the recurring patterns across engagements of this type. What varies by market is which of them carries the most consequence, and in San Jose that is shaped by software and SaaS 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 San Jose specifically, the framing that produces the most useful engagement follows from the local picture: in Silicon Valley the product is the perimeter. Companies here are typically strong on infrastructure hygiene and weak on authorisation logic, because the former is automated and the latter is application-specific. 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 software and SaaS 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 California this matters concretely: the breach-notification clock runs 30 days, 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 San Jose

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.

• SOC 2 Type II
• ISO/IEC 27001
• Customer security questionnaires
• GDPR (where EU data is processed)
• CSA STAR
• IEC 62443
• NIST CSF 2.0
• CMMC (defense supply chain)
• Customer supplier-security audits
• ITAR / EAR export controls
• CMMC Level 2
• NIST SP 800-171
• AS9100 (quality, security-adjacent)
• DO-326A (airworthiness security)
• California breach notification — consumer notice 30 days
• California Consumer Privacy Act, as amended by the CPRA (CCPA/CPRA)

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.

Any SaaS platform holding customer data long-term inherits its customers’ retention risk. Enterprise security questionnaires have begun asking about post-quantum readiness directly, and being able to answer that question with a graded, dated attestation is a commercial advantage before it is a security one.

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 San Jose?

Yes. Secuur serves San Jose and the surrounding California 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 California?

California requires consumer notification 30 days. Sample consumer notice to the AG within 15 days when 500+ residents are affected. 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 software and SaaS 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 San Jose