Demo walkthrough
This is a 20-minute demo that tells one story: something suspicious happens, Identiguard notices, the analyst understands it, the right people are told, and the board gets a report.
Before the demo
Section titled “Before the demo”Check these the day before. Several features are off by default and need an operator to switch them on.
- You can sign in to the demo workspace with your passkey on the laptop you will present from.
- The workspace has at least one tenant for each platform you want to show, and events have arrived in the last 24 hours.
- Incidents appears in the sidebar and has at least one escalated incident.
- Alerts appears under Workspace in the sidebar. If not, ask an operator to switch on alert integrations.
- Journeys appears in the sidebar, if you plan to show it. If not, ask an operator.
- A completed report exists under Reporting → Reports. A report can take up to 90 minutes to generate, so you cannot make one live.
- The Alex panel is authorised. Open it once and choose Authorize Ask Alex.
- Sound is muted on your laptop, or Mute alert sounds is on under Policies. New events play a sound.
The script
Section titled “The script”1. Dashboard (3 minutes)
Section titled “1. Dashboard (3 minutes)”Open Dashboard.
- Point to Needs attention: “This is the first thing an analyst sees. Open incidents, the worst ones first.”
- Point to Workspace statistics: events in the last 24 hours, and the split between Okta, Entra ID and Auth0.
- Point to Tenant status: “Every connected platform, and whether it is healthy. For Okta you also see the AD and LDAP agents and whether they need an upgrade.”
- Scroll to the Event feed: “This is live. If someone fails a sign-in now, it appears here in seconds.”
2. One event (2 minutes)
Section titled “2. One event (2 minutes)”In the feed, choose View on a WARN or ERROR event.
- Show the actor, target, message and raw payload.
- Choose View in Okta to show that it links straight back to the source, if it is an Okta event.
- Mention Raise Ticket and Dismiss Event.
3. An incident (5 minutes)
Section titled “3. An incident (5 minutes)”Open Incidents, choose the Escalated tab and open an incident.
- Attack story: “Identiguard has put these events in order and labelled the stages, from credential access through to a privilege grant.”
- What fired: “This is the detector that noticed, in plain language.”
- Open the score: “The score is not a black box. It shows what it is built from.”
- Evidence: the timeline of events, with the trigger marked.
- Choose Ask Alex AI and ask “What should I check first?”
- Show Close incident and its three reasons, without closing it. Mention that closing as False positive can silence the same pattern on that tenant.
This is the centre of the demo. Take your time here.
4. Correlations (3 minutes)
Section titled “4. Correlations (3 minutes)”Go back to the Event feed on the dashboard, choose View on an event from the same identity, and choose Explore correlations. If the graph is empty, widen the time range and choose Run Correlation.
Evidence rows inside an incident have no actions, so start from the feed.
- Show the Entity graph: “Each dot is an identity, an address or an application. A line means they share events.”
- Select an IP address and choose Focus: “Which other identities used this address?”
- Scroll to Findings: “These are patterns Identiguard found in this window, each with a next step.”
5. Alerts and tickets (2 minutes)
Section titled “5. Alerts and tickets (2 minutes)”Open Alerts under Workspace.
- Show the Slack, Microsoft Teams and Email cards.
- Point to Minimum severity and Tenant forwarding scope: “Each channel chooses which tenants and which severities it receives.”
- If ServiceNow is connected, go back to an event and choose Raise Ticket.
6. Status and advisories (1 minute)
Section titled “6. Status and advisories (1 minute)”Open Okta status or Entra ID status in the sidebar.
- “If Okta has an outage, your team sees it here, beside your own events, with no need to check another site.”
7. Reporting (3 minutes)
Section titled “7. Reporting (3 minutes)”Open Reporting → Reports and choose Download PDF on a completed report.
- Walk through two or three pages. Choose sections that match the client’s platform. See What each report contains.
- For Okta, open Compare, choose two reports and show the What changed tiles.
8. Close (1 minute)
Section titled “8. Close (1 minute)”Go back to Dashboard.
- “Everything you saw works from the moment a tenant is connected. A new workspace gets a 30-day trial of the full platform, with no card.”
- Offer to connect one of their tenants in a follow-up session. See Quickstart.
If you have more time
Section titled “If you have more time”- Journeys for a client with customer sign-in on Auth0. See Synthetic journeys.
- AI clients: show Claude answering a question about the workspace through the MCP server. See Connect an AI client.
- Auth0 API metrics for a client worried about rate limits.
If something goes wrong
Section titled “If something goes wrong”| What you see | What to do |
|---|---|
| The feed chip reads Connecting… | Reload the page. The live connection restarts. |
| A sidebar item is missing | The feature is switched off for the workspace. Move on and mention it by name. |
| The Alex panel asks you to authorise | Choose Authorize Ask Alex. It takes a few seconds. |
| The correlation graph is empty | Widen the time range and choose Run Correlation |
| Anything else | See Troubleshooting |
| No escalated incidents | Use the All tab and open a closed one. |