Cyber controls
Assess the configured control library, record evidence and expiry, and track actions raised from unmet controls.
Bring cyber-control assessments, website checks and supporting evidence into a workflow your school leadership team can review.
Assessments reflect the answers and evidence your team records. Website checks add another source of information; they are not a full penetration test.
Assess the configured control library, record evidence and expiry, and track actions raised from unmet controls.
Review HTTPS behaviour, TLS and available security-header checks. Interpret the results with your website provider.
Where WordPress is detected and WPScan is configured, review vulnerability warnings. Unavailable scans are shown explicitly.
Use specialist cyber reports alongside the whole-school governor report, with risks and open actions in context.
Choose an example outcome to see how it should be interpreted.
Ask your website provider to enforce HTTPS, then run the domain checks again and review the result.
The application shows a notice before a domain check. Checks can request website pages, follow redirects and use WPScan when available. Run checks only for sites you are authorised to assess.
A passing check covers the specific item tested at that time. It does not guarantee that a site is secure. Record actions, review findings and repeat checks after changes.
No. Results depend on the enabled tools, available vulnerability data, website access and scan limits.
The application reports that state. A missing scan result must not be treated as a pass.
The trust dashboard includes cyber readiness where enabled and assessed. School-specific evidence and specialist reports retain their own detail.
AI-assisted policy review, evidence retrieval and website improvement help your team turn information into practical next steps.
Explore private AI ↗IGNX combines school-scoped retrieval with configured AI services. AWS deployments can process document evidence using managed models through Amazon Bedrock.
Model provider, processing region, storage and data residency are agreed before rollout. Local deployments can use a self-hosted model.
Retrieval brings relevant evidence into AI-assisted analysis. Review outputs against the source documents and current guidance.
School records are scoped through account permissions. Authorised trust users can review their linked schools; platform administrators have broader access.
Agree model hosting, storage, retention and access before rollout. Access segregation does not mean every school has a separate database or server.
AI processing follows the configured provider and data boundary. Website crawling, vulnerability checks and email may contact external services when enabled.