E-learning · awareness campaign
Operational cyber compliance
Cyber obligations, organised for action.
Standards, audits, customer requirements, directives and regulations: Torus connects awareness, documents, risk analysis and evidence into one working thread.
- Consultants, CISOs, European SMBs and mid-market teams
- ZDR (Zero Data Retention) on AI exchanges
- Human validation on deliverables
Evidence attached
To review
To validate
In progress
The problem, named
Standards, audits and customer requirements accumulate.Documents remain scattered.
Each framework brings controls, evidence and deadlines. Real work often lives in files, conversations and spreadsheets that do not tell the same story.
What Torus does
From requirement to deliverable,without a break.
The platform connects what needs to be understood, done, validated and presented. Modules remain visible, but the working thread comes first.
- 01
Requirement
A standard, directive article, customer request or auditor question.
- NIS2 · art. 21
- ISO 27001 · control
- Customer RFP request
- 02
Work
A campaign to launch, a document to prepare, a risk to arbitrate or evidence to review.
- E-learning campaign
- Cyber Assistant draft
- ISO 27005 workbook
- 03
Deliverable
Material tied to its sources, reviewed by a human, ready for audit, committee or client work.
- PDF report
- Excel workbook
- Summary note
Evidence is not an abstract promise: it comes from work that was trained, documented, analysed and validated.
Module · Cyber Assistant
Ask a question.Torus answers with your documents and cites its sources.
Cyber Assistant reads policies, procedures and requirements added to the client workspace. It cites the passages used, adds cyber/compliance expertise when the document context alone is not enough, and prepares drafts for review.
- Client documents first. The assistant starts from documents added to the client workspace and made available to the chatbot.
- Visible sources. Each answer shows the passages or documents used.
- Drafts, not automatic release. Notes, checklists or matrices remain subject to human validation.
Does our access review procedure cover what the auditor expects on frequency and managerial validation?
The procedure covers frequency and the roles involved. Managerial validation is mentioned, but no attached evidence confirms it. I can prepare a summary note and a checklist for validation.
In progress
Module · E-learning
Train the teams,and keep the evidence.
Campaigns, learners, reminders, indicators and exports: awareness becomes a work programme, not a yearly send-out that is hard to justify.
- Torus courses. Courses are provided by Torus; customers are not expected to upload their own SCORM packages.
- Reminders and tracking. See what progresses, what remains open and which populations need reminders.
- More courses in preparation. The catalogue evolves progressively, without making e-learning the whole platform.
Module · Risk Analysis
ISO 27005 risk analysis,delivered in Excel.
A pragmatic workflow to structure context, assets, scenarios, assessment and treatment. AI accelerates preparation; the team keeps the arbitration.
- Guided steps. Work moves through successive validations, not opaque generation.
- Standalone workbook. Excel remains readable, shareable and compatible with MONARC practices.
- Human validation. Proposals must be reviewed and arbitrated by the team.
Traceability
In the end, what matters iswhat you can present.
Evidence is not a separate module. Every action in Torus should produce a usable trace, tied to its source and understandable by an auditor.
Risk analysis · working workbook
Cyber Assistant · sourced draft
Consolidated export · sources and decisions
If a question comes back during an audit, the team can find the document, decision, evidence and person who validated it.
Security & data
Your documents remain yours.Nothing leaves without review.
Security shapes how the assistant, documents, campaigns and evidence are used. Torus must stay conservative by design.
View Security & data- 01 Separated client spaces.
Contexts and work scopes remain separated.
- 02 ZDR on AI exchanges.
Zero Data Retention: AI exchanges are not retained for training.
- 03 Approved documents.
The chatbot only uses documents added to the client workspace and made available.
- 04 Human validation.
Answers and deliverables remain material to review before release.
Demo
A demo on your obligations,not on the platform.
We review your requirements, campaigns, documents, risks and evidence needs to see where Torus takes over, and where it does not.
- Human response
- Demo in French or English
- No commitment