Automated scanning in San Francisco.

Why San Francisco organisations commission automated scanning

San Francisco is the densest concentration of venture-backed software companies in the world, with major fintech and biotech alongside. 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

San Francisco companies are usually testing because an enterprise deal requires it, not because a regulator does. That makes the report a commercial document as much as a technical one — the audience includes a prospect’s security team, and the attestation letter frequently matters more to the buyer than the finding detail. Fintech operations layered on top bring genuine regulatory obligation to a subset of the market.

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.

Financial services

Financial institutions are targeted less for disruption than for durable value: account credentials, wire-initiation paths and the account data that funds downstream fraud for years. The attack chain that matters is rarely a single exploit — it is a phished credential, an over-permissioned service account, and a lateral path to the payments environment that nobody mapped because it crossed two teams.

PCI DSS 4.0 requires segmentation testing on top of the penetration test itself, and the GLBA Safeguards Rule makes annual testing an explicit obligation rather than a best practice.

Biotech and life sciences

The asset is intellectual property with a decade-long development cycle: assay data, trial results, manufacturing process detail. The adversary is frequently seeking a research advantage rather than a payday, which changes the profile — the goal is quiet persistence and exfiltration, not disruption you would notice.

Validated GxP environments constrain how and when testing can run, so scheduling and change-control planning matter as much as methodology.

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 Francisco 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

The economics of manual testing put a hard ceiling on coverage: you test the important things annually and the rest never. Automated scanning inverts that. Every asset gets tested on a schedule, the marginal cost of adding the two-hundredth domain is close to zero, and human attention is spent on the findings rather than on the scanning.

The trap is volume. A fleet-wide scan that emits four thousand findings every week trains everyone to ignore it. Secuur reports diffs by default — what appeared, what disappeared, what changed grade since last run — so the weekly output is a short list of actual events.

1. Import assets

From attack-surface discovery, a CSV, or the API. Group them by owner and criticality.

2. Set cadence & routing

Choose a schedule per group and where its alerts go. Rate budgets protect your own capacity.

3. Receive diffs

A short weekly digest of what changed, plus immediate alerts for anything urgent.

Working with San Francisco 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

Continuous scanning earns its place by catching regressions between deeper assessments. Its characteristic value is not depth — it is noticing the change that nobody announced.

Cipher and protocol downgrades

A load balancer replacement or library rollback quietly reverting TLS configuration, including losing hybrid post-quantum key exchange that was previously negotiated.

Certificate expiry approaching

Expiry is an availability incident with a known date, and it remains one of the most common causes of self-inflicted outages.

Newly disclosed vulnerabilities in known software

The window between public disclosure and mass exploitation is now measured in days, so the question is whether you learn about it before the scanning botnets do.

None of the above is hypothetical or specific to San Francisco — 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 Francisco that is shaped by software and SaaS and financial services exposure more than by anything else.

How to prepare

Decide the alert routing before the first scan, not after. A scanner emailing an unmonitored shared mailbox is an expense with no security value attached to it.

In San Francisco specifically, the framing that produces the most useful engagement follows from the local picture: san Francisco companies are usually testing because an enterprise deal requires it, not because a regulator does. That makes the report a commercial document as much as a technical one — the audience includes a prospect’s security team, and the attestation letter frequently matters more to the buyer than the finding detail. 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 Francisco

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
• GLBA Safeguards Rule
• PCI DSS 4.0
• FFIEC CAT
• NYDFS Part 500 (where applicable)
• 21 CFR Part 11
• GxP validation
• HIPAA (clinical data)
• NIST SP 800-171 (federal grants)
• California breach notification — consumer notice 30 days
• California Consumer Privacy Act, as amended by the CPRA (CCPA/CPRA)

The layer nobody else tests

Migrating to hybrid post-quantum key exchange is a project with an end date. Staying migrated is not. Infrastructure changes hands, terminators get replaced, a provider updates a default — and the endpoint you fixed in March is classical-only again by September with nothing to tell you.

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

• Scheduled scanning across your full asset inventory
• Diff-based weekly digest per asset group
• Immediate alerts for critical changes
• Certificate expiry escalation
• Retained grade history and trend reporting
• JSON API and webhooks for your own systems
• Per-endpoint A–F post-quantum readiness grade
• Attestation letter suitable for customers and auditors

Frequently asked questions

Will scanning affect our production performance?

Scans run within a rate budget you set per asset group, and the default is deliberately conservative. For sensitive systems you can also restrict scanning to a maintenance window.

How do you stop alert fatigue?

Diff-based reporting. After the first baseline run you are only told about changes — a new finding, a resolved one, a grade that moved. Unchanged findings live in the dashboard, not in your inbox.

Can we scan internal systems that are not internet-facing?

Yes, via a lightweight collector deployed inside your network that runs the same checks against internal targets and reports back over an authenticated channel.

How does this relate to Secuur Watch?

Watch is the productised subscription tier of continuous scanning, focused on post-quantum posture with a customer-facing attestation. Automated scanning is the broader engine underneath it, covering general vulnerability and configuration checks as well.

Do you provide automated scanning in San Francisco?

Yes. Secuur serves San Francisco 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 Francisco