Limnn Gate is a standalone security portal, orchestration-first and assisted by Cortex. It brings endpoint posture, detections, incident response and compliance into one place, and connects to the workspace's identity and user data so security findings map to real people and devices.
What Gate covers
- Governance - policies, compliance mapping and reports (/gate/govern, /gate/policies, /gate/compliance, /gate/reports).
- SOC monitoring - detections, alerts, timeline and incidents (/gate/detections, /gate/alerts, /gate/timeline, /gate/monitor).
- Endpoint posture - enrolled devices and their health (/gate/devices, /gate/endpoints, /gate/posture, /gate/patch).
- Response and automation - containment, playbooks, triggers, scripts and schedules (/gate/containment, /gate/playbooks, /gate/triggers, /gate/scripts, /gate/schedules).
- Identity - the user center for people-centric security views (/gate/identity, /gate/user-center).
- Administration - sites, team and agent deployment (/gate/sites, /gate/team, /gate/agent).
Getting started
- 1Open /gate and enable Gate for your workspace if it is not already on.
- 2Create sites at /gate/sites to group devices by office, customer or business unit.
- 3Deploy the posture agent from /gate/agent to Windows endpoints and confirm they appear at /gate/devices.
- 4Apply a baseline policy from /gate/policies to your sites.
- 5Review /gate/posture for gaps such as missing patches or disabled protections.
- 6Set up alerting and playbooks so detections trigger the right actions.
Cortex SOC
The Cortex SOC panel triages detections, summarizes incident timelines and recommends next steps. As everywhere in Limnn, Cortex insight is on demand: you ask and choose Execute, and any action it proposes needs human approval.
Scripts are the most sensitive capability in Gate. Technicians cannot self-approve high-risk scripts; a separate approver must sign off, and every run is recorded in the audit trail.