Brief Nebula in plain language. It organises tasks, carries out authorised security work and brings back evidence, reports and updates for your team to review.
Give the engineer an objective. Keep the context and the decisions connected as work progresses.
Explain the goal, share useful documents and define what is authorised.
Keep objectives, tasks and planned reviews together in the engineer workspace.
Nebula works through the task using available tools. Review progress and requested decisions.
Inspect the evidence, refine the report and decide what to share or test next.
The engineer workspace connects the work with the ways your team communicates.
Allowed contacts can reach the engineer through its configured email address. Review received mail and the related conversations in the workspace.
A configured phone channel supports calls and voicemail. See calls the engineer placed or received, with available voicemail transcripts and recordings.
Ask Nebula to prepare a deck. Preview the slides and approve what it may present in a supported meeting. Approval can be removed.
What was tested and what needs attention.
The targets, access and tested conditions.
Impact, reproduction and remediation.
Findings can include impact, reproduction steps, proof and remediation. Verification states distinguish confirmed results from work that still needs review.
Prepare Word and PDF deliverables alongside PowerPoint presentations. For security reports, edit the narrative, choose findings, protect sections from AI changes and review the saved PDF before sharing.
Keep follow-up tasks on the board and planned work on the calendar. After a fix, ask Nebula to retest the original issue.
A severity label is a starting point. Review what was observed, how it was reproduced and which evidence supports the result.
Two authorised test accounts and a shared report endpoint.
One account can retrieve a report owned by the other.
The request, response and steps explain the access-control issue.
Inspect the proof, apply the ownership check and test the same case again.
Start with the systems you are authorised to assess. Scope, access and the tested conditions shape the result.
Investigate authentication, access control and application behaviour with relevant test accounts and context.
Discuss mobile, cloud, infrastructure and AI testing requirements. Confirm the necessary access and supported setup before the work.
Inspect the evidence, agree a fix and return to the same issue. Tests and retests consume plan credits.
We can walk through the context, tools and deliverable your team needs.