Leveraging software orchestration for reshaping the service graph
Security orchestration is the core element of the ASTRID conceptual architecture, including both service management and situational awareness.

Starting from the descriptive and applicative semantics of a Security Model, orchestration is expected to deploy and manage the life-time of the service, by adapting the awareness layer of individual components and the whole service graph according to specific needs of detection algorithms. This means that monitoring operations, types and frequency of event reporting, level of logging is selectively and locally adjusted to retrieve the exact amount of knowledge, without overwhelming the whole system with unnecessary information. The purpose is to get more details for critical or vulnerable components when anomalies are detected that may indicate an attack, or when a warning is issued by cyber-security teams about new threats and vulnerabilities just discovered.
Decoupling detection from monitoring and inspection
ASTRID pursues a transition from infrastructure-centric to embedded service-centric cybersecurity frameworks.

The main concept is the disaggregation of cyber-security appliances into business logic (i.e., detection algorithms) and data plane (i.e., monitoring and inspection tasks), mediated by orchestration logic and proper security models. Instead of overloading the execution environment with complex and sophisticated threat detection capabilities, efficient processing capabilities are provided in the execution environment that create events and knowledge. Algorithms for detection of threats and vulnerabilities are moved upwards and process such data in a coordinated way for the whole execution environment.
In-kernel processing for fast inspection & effective enforcement
In-kernel processing for fast inspection and effective enforcement

ASTRID designs and develops a software data plane leveraging eBPF and related frameworks. The target is a flexible data plane well beyond the basic monitoring capability today envisioned by flow-level reporting, which includes stateless and/or stateful inspection criteria on flows and/or packets, aggregation and storing capabilities. ASTRID defines the data plane as the logical layer between the user-requested service and the external word, including the virtualization system, network processing elements (e.g., software switches), and hypervisor/operating systems internals (e.g., system calls). Thanks to this broad definition, ASTRID may exploit multiple and advanced programmability features of the data plane to perform monitoring, inspection and enforcing tasks, ranging from applications running in VMs or containers (e.g., LXC), OpenFlow rules, IOVisor and/or P4-based applications.

Latest News | View all
ASTRID – funded by the European Commission
ASTRID Consortium receives formal notification of acceptance from the EC.
Jan 15, 2018
ASTRID kick-off meeting in Genoa
ASTRID kick-off meeting held in Genoa
May 31, 2018
Fulvio Risso attends Netdev 0x12
Fulvio Risso attends the Netdev 0x12 Conference in Montreal
July 13, 2018
Stefan Covaci at COMPSAC 2018
Stevan Covaci presents the ASTRID project at COMPSAC 2018.
July 30, 2018