Tool Architecture
Interfaces to Greenbone Security Solutions
Three interfaces to the Greenbone Security Solutions are available. They cater for
- experts such as security auditors, who need fine-grained configuration and thus use the very comprehensive graphical user interface.
- low level integration of the scan-engine, as needed for example by security appliances and ISP customer products. The command line interface allows for easy use in automatic batch processes.
- vulnerability management, where the focus is threat status, threat trends and easy reporting, as well as high level integration into network management. This is what the Greenbone Security Assistant is designed for.
Component Architecture
The internal architecture follows the approach of task-oriented components. In other words, instead of an all-in-one-tool, each task is designed as a service. For example, the OpenVAS Manager is a client of the Scanner service. At the same time the OpenVAS Manager is a service for the OpenVAS Client or the Greenbone Security Assistant.
- Small, focussed components can be implemented and operated transparently and securely. Each components uses only the system privileges that it needs to operate properly.
- Each of the service components offers a well-defined comunication protocol.
Source Code Architecture
The structure of the source code supports the component-oriented and security-aware tool architecture:
- avoid redundant source code: any code used by more than one component is part of one of the five libraries.
- avoid dependencies on non-common third-party code: rely only on widely used and proven core libraries.
