1. Overview
ITSELECT Executive Cockpit turns technical, organisational and governance signals into executive indicators. It is not designed to replace a SOC, SIEM or full ITSM platform. Its purpose is to give decision-makers a clear view of digital exposure, maturity, priorities and progress over time.
2. Roles and access
The platform relies on strict role separation. A client only sees its own organisation, domains, scans, diagnostics, reports and authorised users. ITSELECT administrators supervise active clients, accounts, logs and platform configuration.
| Role | Purpose | Main access |
|---|---|---|
| itselect_admin | Global administration | All clients, users, logs, reports, settings and administration pages. |
| itselect_consultant | Advisory follow-up | Assigned clients, diagnostics, scans, reports and operational support. |
| client_admin | Client manager | Organisation, domains, scans, diagnostics, client profile and users within scope. |
| client_viewer | Read-only access | Executive view, history, risks and reports for the organisation. |
3. Client profile and modules
The client profile is the organisation reference point. It gathers the core information required to interpret scans, diagnostics and reports correctly.
4. Executive cockpit
The main page consolidates technical health, IT governance, NIS2 and DORA when these diagnostics are enabled. It must help an executive understand what is under control, what remains exposed and which actions should be launched.
- Consolidated view by pillars: technical, governance, NIS2, DORA.
- Top priority risks and 30 / 60 / 90-day roadmap.
- Contextual messages depending on enabled modules.
- Clear separation between public demonstration and authenticated client cockpit.
5. Automated controls
The Controls module analyses visible fundamentals of the organisation. Results are saved in history to compare progress over time.
6. Microsoft 365 Lite
Microsoft 365 is connected through read-only Microsoft Graph access. The client grants administrator consent, then the cockpit reads only the information needed for governance assessment.
- Tenant and domain information.
- Users, guest accounts and disabled accounts.
- Administrator roles and governance signals.
- Reports available according to granted permissions.
- Secure Score when the additional permission is enabled.
7. Risk Engine
The Risk Engine converts technical results and diagnostic answers into understandable risks. It avoids showing a raw list of controls and produces a prioritisation that management can use.
Each risk can be new, persistent, resolved, worsened or improved. This makes it possible to track real progress beyond a simple point-in-time score.
8. Integrated diagnostics
Diagnostics complement automated scans with maturity and governance analysis. Each diagnostic can be enabled or disabled per client.
DORA can remain disabled by default when the organisation is not a financial entity or a critical ICT supplier to a financial entity.
9. History and progress
History keeps scans and allows teams to track score, control and risk evolution. For a client user, the view remains strictly limited to their organisation.
- Latest scan and previous scan.
- Evolution by domain and pillar.
- New, resolved, persistent, improved or worsened risks.
- Detailed findings and traceability by date, client and domain.
10. Board-level reports
Reports convert results into documents that a management committee, board of directors or monthly review meeting can read. They can be printed as browser PDF, sent by email and archived in the report history.
11. Multi-client administration
The ITSELECT admin space manages clients, domains, users, invitations, password resets, enabled diagnostics, scheduled scans, logs and operational settings.
For the ITSELECT_Admin profile, the default landing page is administration: /cockpit/admin.html in FR and /cockpit/en/admin.html in EN.
12. Mini-CRM
The mini-CRM complements the cockpit with a simple commercial and relationship view, without turning ITSELECT into a heavy CRM tool. It tracks clients, prospects, context, status, next actions and opportunities linked to diagnostics or scans.
- Centralise useful advisory follow-up information.
- Prepare follow-ups after a diagnostic or report.
- Document exchanges without collecting unnecessary data.
- Keep commercial steering separate from technical data.
13. Logs and traceability
Logging is structured to provide visibility without exposing unnecessary sensitive data. It helps understand actions, errors and cockpit usage.
14. Security and good practices
The cockpit should remain restrained in the data it collects. It stores scores, statuses, risks, recommendations, reports and useful logs, but should not collect unnecessary content such as emails, SharePoint files, passwords or excessive personal data.
Recommended use
For a pilot client, ITSELECT can start with a monthly technical scan, a quarterly governance diagnostic, a NIS2 review where relevant and a board-level report after each cycle.