Skip to main content
Exposure management

Know the assets. Review the risk.

Bring recorded assets, testing context and findings into one review. Decide what needs investigation, what the evidence establishes and where to return after a fix.

Book a demoExplore plans
Illustration of a known asset inventory connected to a scoped review and an evidence record
Inventory, investigation and evidence, illustrated.

An inventory with context.

Move from a hostname to the details that help your team decide what to assess.

Illustrative asset review
  • Applicationapp.example.comHTTPS service recorded
    Finding linked
  • API hostapi.example.comService details available
    Needs review
  • Test environmentstaging.example.comContext to confirm
    Not assessed
Example records, not a live inventory. An asset without a finding is not evidence that it has been tested.

Review the assets already recorded

Explore the inventory by engagement or across available engagements. Search and group records, then inspect a domain, host, address or endpoint.

Look beyond the name

Where recorded, asset detail includes ports, services, technologies, timestamps and screenshots. Sparse records remain visible without inventing missing data.

Open the findings that belong to it

Explicit asset associations connect a record to its findings. Review their evidence and verification state before deciding on remediation.

Choose the next meaningful test.

Use the inventory to form a clear brief for the engineer, with the target, access and limits the work requires.

Confirm the target

Select systems you are authorised to assess. Record the relevant domains, hosts, ranges or assets and exclusions in the engagement context.

Supply useful context

Share the application purpose, test accounts, API details and constraints. Credentials and network access shape what a test can establish.

Investigate the question

Ask Nebula to examine the behaviour that matters, such as an access boundary or an exposed service. Review progress, evidence and requested decisions.

Keep the review connected to the fix.

Plan. Run. Review. Return.

Planned workEvidence to assessA fix to verify

Prioritise from the evidence

Use the recorded severity, impact and reproduction details to decide what needs attention. Keep incomplete or unverified results distinct from confirmed evidence.

Plan the follow-up

Connect the next task with the engineer board or calendar. After your team makes a change, request a retest of the original condition and review the new result.

Report what was established

Prepare a report around the tested scope, findings and remaining questions. Tests and retests use the credits available in your plan.

From inventory to action.

Follow the evidence

See how context, observations and proof support a finding.

Plan the next review

Connect recurring work, remediation and retesting.

Discuss a scoped engagement

Agree the assessment you need and the access it requires.

Start with an asset you need to understand.

Bring the target, the question and the access available. We can walk through the review together.

Talk through your scope