VULCANSECURITY

Start with a scope,not a sales call.

Tell us what to test and how to reach you. A Vulcan lead reviews every request by hand, confirms authorization, and replies with the right scope before any testing begins.

How we work
CommitmentWhat it means
ConsentWe test only targets you own or are authorized to request. Scope is confirmed before any work starts.
Data saleWe do not sell your information or share your codebase. Findings stay between your team and Vulcan.
ValidationWe prove an issue, capture the evidence, and stop. We do not exploit findings beyond what is needed to validate them.
ReportingEvery finding is reported directly to you. There is no third party in the loop.
HostingClient data is held on third-party infrastructure. Vulcan does not maintain its own servers.
What happens next
01We review the target and confirm authorization.
02A lead replies with scope, timing, and pricing.
03Testing starts only after you approve the plan.

Assessment request

Tell us what to test.

A lead reviews every request by hand. We will confirm the target, scope, and timing before any testing begins.

Where the scope confirmation goes.

What should we test?

The production or staging URL we should start from. Add the login path if it is separate.

Vulcan tests only with consent. We do not sell or share your information or codebase, do not exploit findings beyond what is needed to validate them, and report directly to you with no third party. Read the Terms and Privacy Policy.

A lead replies within one business day. No testing starts until scope and authorization are confirmed in writing.

By sending this request you agree to the assessment terms and privacy policy.