Notifications
NodeZero will send email notifications for the following events that occur during the operation lifecycle.
State types:
- informational
- action required
| Event / State | Type | Description | Sent To |
|---|---|---|---|
| Pentest started | NodeZero has launched and successfully connected back to the one-time-use ephemeral architecture to start the pentest | The user who created the pentest | |
| Pentest completed | The pentest completed and results are available in the Portal | The user who created the pentest | |
| Pentest paused | |
The pentest paused due to lost connectivity with NodeZero | The user who created the pentest |
| Pentest resumed | The pentest resumed after being paused | The user who created the pentest | |
| Pentest expired | The pentest never launched and was auto-canceled after 12 hours | The user who created the pentest | |
| Paused pentest canceled | The pentest was stuck in a paused state for over a week and was auto-canceled | The user who created the pentest | |
| Pentest waiting for NodeZero | |
The pentest was created, but has not yet launched, because NodeZero has not yet connected back the H3 cloud | The user who created the pentest |
| Pentest ready to start | |
The pentest launched in a paused state, typically for whitelisting NodeZero's IP, and is waiting to be started by the user | The user who created the pentest |
| Scheduled action initiated | The scheduled action was successfully initiated at its scheduled time, e.g. creating a scheduled pentest via the h3-cli or Portal | The user who created the scheduled action | |
| Scheduled action failed | |
The scheduled action failed to run | The user who created the scheduled action |
| NodeZero Runner hit an error | |
The NodeZero Runner failed to launch NodeZero | The user who created the Runner, along with the user who created the pentest that failed to launch |