> For the complete documentation index, see [llms.txt](https://docs.cybaops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybaops.com/getting-started/what-is-cybaops.md).
# What is CybaOps?
*One platform to see your risks, stop attacks and prove you are secure*
CybaOps is a cyber security operations platform that brings everything you need to protect your organisation into one place. It shows you what you own, watches for attacks around the clock and helps you respond quickly, all from a single login. CybaOps closes the loop: it finds and fixes weaknesses before attackers can exploit them, and learns from every threat to stop the next one taking hold. Instead of juggling separate tools for assets, vulnerabilities, monitoring and compliance, you get one joined-up view of your security and a clear list of what to do next.
***
## Getting Started
Most organisations are up and running in four simple steps. The first time an organisation admin signs in, the onboarding wizard guides you through the first three. See [Onboarding](/getting-started/onboarding.md) for the full walk-through.
{% stepper %}
{% step %}
### Confirm your company details
Accept the user agreement and check your organisation's [company details](/settings/settings-overview.md#company-details).
{% endstep %}
{% step %}
### Deploy the agent
Install [CybaAgent](/getting-started/onboarding/agent-deployment.md) on your Windows, macOS and Linux devices.
{% endstep %}
{% step %}
### Connect your tools
Connect Microsoft and the other security tools you use with [Connectors](/getting-started/onboarding/connectors.md).
{% endstep %}
{% step %}
### Complete your Security Assessment
Answer the [Security Assessment](/identify-and-protect/security-assessment.md) questions to set your security baseline.
{% endstep %}
{% endstepper %}
***
## A Tour of the Platform
CybaOps is organised into modules that follow the way security work actually happens: know what you have, protect it, detect and respond to attacks, prove compliance and report on it.
### Identify & Protect
You can't protect what you don't know about, so this is where everything starts.
* [**Asset Manager**](/identify-and-protect/asset-manager.md) builds a single inventory of your devices, users, websites and other assets, combining CybaAgent, connectors such as Microsoft Entra ID and anything you add by hand. It shows which assets are protected and which are missing the agent, so gaps don't go unnoticed.
* [**Vulnerability Management**](/identify-and-protect/vulnerability-management.md) lists the weaknesses found on your assets, ranks them by severity and tracks them until they are fixed, so your team works on the issues that matter most first.
* [**Security Assessment**](/identify-and-protect/security-assessment.md) is a guided questionnaire that grades how well your policies and processes match good practice, and gives clear advice on where to improve.
### Detect & Respond
This is where attacks are spotted and stopped.
* [**Managed Detection and Response (MDR)**](/detect-and-respond/managed-detection-and-response-mdr.md) is the CybaVerse service that monitors your organisation around the clock, investigates anything suspicious and contains real threats in line with your pre-approved actions.
* [**Endpoint Detection and Response (EDR)**](/detect-and-respond/endpoint-detection-and-response-edr.md) is CybaAgent watching what runs on each device, spotting suspicious behaviour and containing it on the device, alongside your existing antivirus.
* [**Investigate**](/detect-and-respond/investigate.md) is the CybaOps SIEM. It collects security events from your agents and connected tools, stores them using the open OCSF standard, and lets you search, build dashboards and hunt for threats.
* [**Case**](/detect-and-respond/case.md) is where incidents are worked. Each incident has a timeline, artefacts such as users, devices and saved searches, and a full record of what was done, so you and CybaVerse MDR always share the same picture.
### Compliance
[**Cyber Essentials**](/compliance/cyber-essentials.md) takes you through the UK government-backed Cyber Essentials and Cyber Essentials Plus schemes inside the platform, using the evidence CybaOps already holds to make certification quicker.
### Reports & Exports
[**Reports & Exports**](/reports/reports-and-exports.md) turns your data into branded PDF reports for leadership and CSV exports for your own analysis.
***
## How It All Fits Together
The modules aren't separate tools bolted together. They share the same data, so work in one place improves the others.
[CybaAgent](/identify-and-protect/asset-manager/cybaagent.md) and your [connectors](/getting-started/onboarding/connectors.md) feed [Asset Manager](/identify-and-protect/asset-manager.md), which gives every other module the same list of what you own. Scan results from the agent become [vulnerabilities](/identify-and-protect/vulnerability-management.md) linked to those assets. Security events from the same sources flow into [Investigate](/detect-and-respond/investigate.md), where detection rules and correlation turn noise into a small number of real incidents in [Case](/detect-and-respond/case.md).
Everything then rolls up. All the data CybaOps collects, from your assets and vulnerabilities to your [Security Assessment](/identify-and-protect/security-assessment.md), feeds the [Security Posture Rating](/getting-started/dashboard.md#security-posture-rating), a single score out of 1000. The platform checks your data continuously and raises [Immediate Actions](/getting-started/immediate-actions.md), a short, prioritised to-do list of the things that will reduce your risk most. The [Dashboard](/getting-started/dashboard.md) brings all of this into one screen.
When something needs fixing, it happens in one of three places: on the incident itself during incident response, through Immediate Actions, or on the case timeline. That keeps every change recorded and easy to review later.
***
## Next steps
* [Dashboard](/getting-started/dashboard.md): See your security at a glance and learn how to read each widget.
* [Onboarding](/getting-started/onboarding.md): Set up your organisation and get your first data flowing.
* [Immediate Actions](/getting-started/immediate-actions.md): Find out what to fix first to reduce your risk.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.cybaops.com/getting-started/what-is-cybaops.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
