FRBook a demo
Home/API & automation
API & automation

Integrate hardening
into your response workflows.

Your security tools detect an anomaly. Your teams define the response. Our goal is to let them control Cyberlib through an API to adapt the configuration of affected endpoints from their own systems.

Let’s talk
PRODUCT VISION

This page presents our goal of a complete API and multi-language SDKs. Available scope, languages and timing should be discussed with our teams for your integration project.

REMOTE CONTROL

An API to integrate Cyberlib
into your information system.

The ambition is to expose the solution’s full capabilities through an API: inspect fleet status, manage hardening templates, trigger operations and use their results. Your applications will be able to integrate Cyberlib into business and security processes.

For the CISO

Define authorised responses

Translate security scenarios into configuration measures prepared in advance. Define trigger conditions, scope and required approvals.

For IT managers and technical teams

Connect existing tools

Plan to control Cyberlib from your orchestrator, ITSM tool or internal scripts without adding a manual intervention chain for every alert.

For the CIO

Govern automation

Decide which actions can be automated according to their service impact. Include operational constraints and business continuity when designing workflows.

ILLUSTRATIVE WORKFLOW

An anomaly detected.
A targeted hardening response.

A security tool detects abnormal use of a remote administration service. Your teams can design a workflow to temporarily strengthen the affected endpoint’s configuration using settings validated in advance.

  1. 01

    Detect

    Your EDR, SIEM or another security tool reports suspicious behaviour on an endpoint.

  2. 02

    Qualify

    Your orchestrator checks signal reliability, identifies the endpoint and selects an authorised workflow.

  3. 03

    Harden

    The workflow calls the Cyberlib API to request application of the prepared configuration within the selected scope.

  4. 04

    Verify

    Your process retrieves the result, arranges a configuration check and updates incident tracking.

Detection stays in your security tools.

Your teams build and orchestrate the workflow. Cyberlib is intended to execute its hardening actions: for example, restrict a service or strengthen access settings, depending on API capabilities and the settings available for the affected system.

API & SDK

Integrations suited
to your development teams.

We aim to provide SDKs in several programming languages to make the API easier to use from your applications and automation. The goal is to simplify calls, response processing and error handling.

Supported languages and functions will be specified as the offering becomes available. Share your technical environment with us to scope your needs.

YOUR ECOSYSTEMPlanned architecture
Applications
Scripts
Orchestrator
Multi-language SDKsIntegration with your tools
Planned
API CYBERLIBControl your hardening
  • Fleet
  • Hardening templates
  • Operations
  • Results
WORKFLOW DESIGN

Automate the response.
Keep control of changes.

Reactive hardening complements your baseline configuration by adapting protection to a specific signal. Its effectiveness depends on a prepared, tested workflow proportionate to the affected service’s needs.

A qualified signal

Define confidence criteria, thresholds and duplicate-alert handling. A single alert should not trigger uncontrolled fleet changes.

Limited scope and permissions

Plan a dedicated service identity and permissions limited to necessary actions. Explicitly target affected endpoints to avoid an overly broad response.

Approval based on impact

Test configurations in a pilot. Retain human approval for sensitive changes or those that may affect critical services.

Verified results and recovery

Plan failure handling, a post-change audit and decision traceability. Returning to the normal configuration should follow an approved procedure after incident assessment.

Let’s design your
integration workflow.

Your detection tool, orchestrator, expected actions and development languages: let’s discuss an initial use case.

Discuss my API project ↗
CYBERLIB

Your questions, answered

What is reactive hardening?

Reactive hardening triggers a targeted configuration change in response to a security event. For example, an anomaly detected by an existing tool can feed an orchestration scenario: select affected endpoints, apply an authorised model and verify the result. Scope, approvals and traceability must be defined before automation.

Define exposure reduction priorities ↗

What is the goal of the Cyberlib API and SDKs?

Cyberlib aims to provide a comprehensive API so customers can operate the solution remotely from their applications, scripts and orchestrators. Multilanguage SDKs are planned to simplify integration. Available interfaces, languages and delivery details should be agreed with the Cyberlib team for each project.

Discuss your integration scenario ↗