Assess before acting
Discover the authorised environment and examine its security posture. Make incomplete checks and detection gaps visible.
AI Defence / The Remedy security programme
See the risk. Understand the recommendation. Control the response.
AI Defence is designed to assess your networks, servers and applications, explain what matters, and verify authorised security changes before establishing a baseline for continuous monitoring.
The whole environment, in context
AI Defence connects what is exposed, what is vulnerable and what has authority. The result is designed to be a decision you can act on, with the evidence to support it.
Discover the authorised environment and examine its security posture. Make incomplete checks and detection gaps visible.
Translate technical evidence into a clear report: what matters, why it matters, and what a change would affect.
Apply only authorised remediation. Retest the security condition and the services that need to keep working.
Security coverage
The specified scope reaches beyond individual hosts to the identities, data and delivery systems they depend on.
Network paths, exposed services, segmentation and the boundaries between systems.
Explore this security area ↗OS posture, patch levels, services, permissions and suspicious runtime changes.
Explore this security area ↗Workload privilege, Docker exposure, image provenance and cloud access.
Explore this security area ↗Accounts, machine identities, SSH keys, excessive permissions and exposed credentials.
Explore this security area ↗Authentication, sessions, API controls, TLS and application exposure.
Explore this security area ↗Data access, encryption, tenant boundaries, backups and audit evidence.
Explore this security area ↗Also explore contextual vulnerability management and software supply chain security.
Risk correlation
An exposed, privileged service can create a different risk from the same software in an isolated test environment.
AI Defence is designed to weigh exploitability, exposure, business importance, privilege and compensating controls together.
How risk is prioritised ↗ILLUSTRATIVE RISK SCENARIO
Prioritise investigation.
Explain the evidence, identify the affected boundary and recommend a controlled response.
A risk example, not a live finding or claim of confirmed compromise.
A governed lifecycle
Inventory the environment. Inspect controls. Record evidence and coverage gaps.
Correlate risk. Produce the report. Explain impact and priority.
Agree the action. Prepare recovery. Apply the change and retest.
Record the accepted state. Detect new exposure, vulnerabilities and drift.
Authority stays with you
The ability to detect a problem is not permission to change your environment.
The first assessment is observational. Recommendations explain possible downtime, dependencies and the order of work. You can authorise everything proposed, selected changes, individual findings or nothing.
Material changes need current-state checks, impact analysis, rollback preparation and protected administrator access.
Read the remediation model ↗One engineering family. Distinct responsibilities.
Security posture, authorised hardening and continuous threat and vulnerability monitoring.
Programme status ↗Software defect diagnosis, source-code repair and verification. From bug report to verified fix.
Remedy AI Bug Fixer ↗The governed autonomous software engineering control plane for delivery around AI workers.
Nexus software engineering ↗Start with understanding
Discuss the assessment scope, current capabilities and the control you need with Altari Systems.