Community

Open source

AarSOC is built exclusively on open-source components. Our own hardening toolkit (cyberaar-toolkit) is published under a free licence: you can audit it, modify it and deploy it in your own infrastructures. The AarSOC platform is not published.

A security tool you cannot inspect is a tool you do not control. This is the principle that guides our technical choices.

cyberaar-toolkit

Collection of Ansible roles for CIS hardening and compliance

GPL-3.0

51 Ansible hardening roles aligned with CIS (Center for Internet Security) benchmarks. Each role covers a precise scope: kernel configuration, network service hardening, account and access management, logging, file integrity.

Systems covered

RHEL 9, Ubuntu 22.04/24.04, Debian 12

Ansible roles

51 independent, composable roles

CIS controls audited

96 controls (Ubuntu and RHEL 9)

Audit report

HTML and JSON output, browsable offline

Dashboard

No external server, usable on air-gapped networks

Licence

GPL-3.0: free reuse, modifications publishable

The audit script generates a self-contained HTML report and a JSON export. The dashboard runs without any connection to an external server, making it usable in air-gapped or restricted-classification environments. Reports can be integrated into your CI/CD pipelines.

GitHub Ansible Galaxy

Our publication policy

What we publish

  • + System hardening tooling (cyberaar-toolkit, GPL-3.0)
  • + Generalisable detection rules in Sigma format, provided they expose no client context

What we do not publish

  • - The AarSOC platform code: publishing it would expose the monitoring architecture of our clients
  • - Research work tied to sensitive client contexts

We publish what strengthens the ecosystem without exposing our clients. For a security company, this boundary is not a commercial reserve — it is a requirement.

Upcoming projects

Detection rules library

MITRE ATT&CK-aligned rules, verified against real data. Compatible with the major correlation engines on the market. Publication in progress.

Coming soon

R&D results

Some results of our research work will be published when they are generalisable and unrelated to any client context.

Coming soon

Contribute

01

Fork & clone

Clone the repository, create a working branch with a name describing the change.

02

Test locally

Use the test environments described in the documentation. Roles are testable with Molecule.

03

Pull request

Describe the change, the systems tested, and the CIS controls affected.