Company / Frequently asked questions
Clarity before the first step.
A good engagement starts with shared expectations. These answers explain the general approach; your proposal defines the specific scope, responsibilities, schedule, and deliverables for your organization.
Clarify the engagement questions
Scope and depth
What is assessed and which tests are agreed
People and permission
Human oversight and authorized activity
Schedule and fee
Terms defined for the proposed engagement
After the readout
Remediation ownership and scoped follow-up
The proposal resolves the scope, responsibilities, commercial terms, and follow-up details.
01 / A CLOSER LOOK
Choose the right starting point.
OPSEQ starts with the outside view of your organization. The assessment can focus on a particular question or a broader public footprint. Hands-on validation, internal access, social engineering, and testing third-party systems need explicit inclusion and appropriate authorization.
FOCUS POINTS
- Start with the business question.
- Match testing depth to the decision.
- Confirm permissions before testing.
02 / A CLOSER LOOK
Plan the engagement around your needs.
The amount of work depends on the breadth of the organization and the depth of validation. Schedule, fees, communication, and retesting are proposal-specific. Share any launch, transaction, or review deadline early so the scope can be discussed in that context.
FOCUS POINTS
- No standard timeline implied by the website.
- Scope and deliverables agreed before commitment.
- Follow-up work included only when explicitly scoped.
BEFORE YOU BEGIN
Common questions.
Is OPSEQ a software platform?
OPSEQ is an AI-assisted offensive security service. AI agents support discovery and research; a human lead directs the assessment and reviews the findings. The engagement delivers an assessment and action plan.
Is this a penetration test?
An outside-in exposure assessment is the starting point. A penetration test involves agreed hands-on testing of specified systems. That depth of validation must be explicitly defined in the engagement.
Can we start with one concern?
Yes. A focused question can help define a useful scope: an internet-facing application, uncertain public assets, a brand-related concern, or a finding that needs a retest.
Do you provide continuous monitoring?
An assessment covers the agreed assets and assessment period. Recurring reviews can be scoped, but they are distinct assessments and do not imply continuous monitoring or incident response coverage.
How much does it cost?
Fees depend on the scope and depth of validation. The proposal sets the fee, schedule, deliverables, and any retest coverage before you commit.
Will you make changes to our systems?
Your team owns remediation. Any test that changes state or requires access must be explicitly authorized in the rules of engagement. Recommendations in an assessment are not permission to change your systems.
Does an assessment certify that we are secure?
No. Findings describe the evidence and limitations within a defined scope and period. The assessment does not guarantee every weakness has been found or provide a compliance certification.