Network exposure assessment
Small Network Vulnerability Assessment
Turn a small, known host set into a credible priority list—not an open-ended discovery exercise.
Published package price and scope. Availability, authorization, and final applicable terms are confirmed before work begins; public self-registration is not currently available.
Service overview
A bounded service for a specific decision.
This package evaluates up to five fixed host identities that are named and authorized before work begins. It is useful when the organization already knows which systems matter and needs a controlled snapshot of network service exposure and likely vulnerability conditions.
The host list does not expand during the engagement. Results are staff reviewed and organized around affected systems, evidence, and action so the customer can distinguish meaningful priorities from raw detection volume.
What this service clarifies
Three questions the work is designed to answer.
The package stays useful by keeping the evidence, output, and decision inside a defined boundary.
- 01
Which services and vulnerability conditions are visible on the named hosts?
- 02
Which detections are credible and relevant to this small environment?
- 03
What should system owners remediate and verify first?
Delivery framework
Controlled from intake through handoff.
Staff time includes preparation, analysis, customer interaction, and reporting—not only meeting time.
- 01
Lock the host list
Confirm up to five exact host identities, authorization, reachability, and approved assessment path.
- 02
Collect the baseline
Assess visible services and, when supported and approved, limited credentialed evidence.
- 03
Validate the signal
Review detections against the affected host, exposed service, and available evidence.
- 04
Prioritize and retest
Deliver the action register and perform one eligible verification against the unchanged host set.
What you receive
Artifacts that preserve scope, evidence, and next ownership.
Exact output reflects the accepted scope and available evidence. Every package retains the boundaries needed to interpret the result responsibly.
Coverage record
The exact hosts, access level, reachability, and material evidence limitations.
Reviewed vulnerability register
Credible findings connected to host and service context.
Prioritized remediation queue
A practical sequence for system and network owners.
Eligible same-scope retest
One verification cycle against the original accepted host identities.
Scope record
What is included—and what is not.
Payment alone does not authorize access, testing, or production change. Named scope, consent, access, timing, and any safety conditions are confirmed before activity begins.
- Network service posture assessment
- Optional supported SSH evidence with validated credentials, at most one role per host
- Staff-reviewed report; one baseline and one eligible same-scope retest
Up to five named, authorized hosts. The accepted host list stays fixed; it is not an open-ended network discovery range.
Expanded network ranges, replacement hosts, full Windows domain audits, lateral movement, agent deployment, continuous monitoring and remediation are not included.
Service window: Intake is due within 30 days after payment. The service term runs for 90 days after scope acceptance, subject to the accepted order terms. These are service windows—not guaranteed turnaround times.
Good fit when
The package matches the question and boundary.
- You have five or fewer known systems to review
- A project or change needs a bounded network vulnerability baseline
- The team needs reviewed priorities rather than a raw scan export
Choose a tailored scope when
The requirement extends beyond the package.
- You need discovery across a subnet or enterprise environment
- You need lateral movement or domain-level attack-path testing
- You need recurring scanning, agents, or ongoing vulnerability operations
Service questions
Practical answers before you proceed.
01Can hosts be swapped after the scope is accepted?
No. The accepted host list remains fixed. Replacement or additional hosts require separate scope so evidence and authorization remain unambiguous.
02Is credentialed evidence required?
No. Limited supported SSH evidence may be used when agreed and when valid credentials are available. Coverage and evidence limitations are recorded in the report.
03Does this include remediation?
No. The package provides reviewed findings and guidance. Configuration changes, patching, and broader remediation assistance require separate approval.
Customer dashboard
Review the package, then continue through the controlled service process.
Existing customers can view the service catalog in the dashboard. Need access? Use the project brief to request customer access without sending credentials or sensitive evidence by email.