Navigate Griffin

Main pages

• Dashboard — review workspace configuration, summary metrics, recent failures, and recent audit activity.
• Applications — create applications, register exact public targets, manage inventory, and complete authorization and ownership.
• Scans — open the dedicated New scan page, select eligible scan types, monitor live progress, inspect status history, and open scan details.
• Schedules — create recurring authorized schedules, add blackout windows, and manage notification preferences.
• Findings — filter passive observations, open evidence, assign remediation, record dispositions, and request retests.
• Reports — generate reports from immutable scan snapshots, review traceability, create time-limited redacted exports, and manage retention.
• Security & guardrails — review the observational checks, enforced safety boundaries, and planned coverage.
• When Griffin retrieves page content, a labelled loading spinner remains visible until the content is ready.

Read the findings list

The Findings page keeps the overview compact. Each row identifies the finding and the application, exact target URL, and latest scan that produced it.

• Select the finding name to review evidence and remediation details.
• Select the application name or target URL to return to that scope.
• Select the full scan ID to review the scan result that most recently observed the finding.
• Use the compact Status and Severity controls to narrow the list. Last seen appears beside the current status.

Read and share a finding

A finding detail page begins with a plain-language summary for managers and developers. It shows severity, priority, confidence, application and target context, why the finding matters, suggested remediation, and the latest scan before the technical evidence.

• Share files include the readable finding summary, application and target, latest scan, suggested solution, and framework mappings.
• Evidence payloads remain inside authenticated Griffin and are never included in share files.
• Management actions and history remain available in collapsed secondary sections so they do not obscure the finding itself.

1. Review Finding summary to understand status, severity, affected scope, and priority rationale.
2. Review Suggested solution and validate the recommendation against the application's intended behavior before making a change.
3. Review Frameworks as traceability only; a mapping is not a compliance, certification, or complete-coverage result.
4. Review Evidence in the terminal-style panel. Griffin shows only bounded, redacted evidence retained for the finding.
5. Use Share at the top-left to download a PDF, Word (.docx), or JSON summary.

Complete application setup in order

The Applications page is a paginated inventory of application grouping records. Creating applications, creating targets, listing targets, and authorizing a target each use separate pages.

An application is a grouping record for one product or system. It holds classification, targets, reporting context, and history. A target is one exact public URL inside that application; authorization, technical ownership, activation, scans, and findings are tracked for that URL.

• Applications lists only applications and provides pagination. Select an application name or View targets to open its separate target page.
• Step 1: Application records the product or system grouping and its classification.
• Step 2: Target registers an exact public URL and its observational scope under an active application.
• The target page lists only that application's targets, provides pagination, and shows Authorization, Ownership, and Activation progress for every visible target.

1. Step 1: Application — select + Add, complete the dedicated page, and save the grouping record.
2. Step 2: Target — select an application name, then select + Add from its target list and register one exact public URL on the dedicated page.
3. Step 3: Authorization — on the application's paginated target page, open a target's Actions menu and select Authorize; record written authorization, verify technical ownership, and evaluate preflight on the target's separate page.
4. Step 4: Scans — open Scans, select + Add, choose the active target and one or more authorized observational scan types, review preflight, and start the scan.

Before submitting a change

1. Confirm the active customer workspace and your permission for the action.
2. Open the page and tab named in the relevant guide.
3. Complete every required field and review the scope or impact shown beside it.
4. Select the named submit button once and wait for the success or error message.
5. Return to Overview or the relevant history view and confirm the new record and status.