Architecture
| Ref |
Feature Name |
Description |
| A1 |
GUI |
The tool offers a graphical user interface (GUI) |
| A2 |
CLI |
The tool offers a command line interface (CLI) |
| A3 |
API |
The tool offers an application programming interface (API) |
| A4 |
On Premise Deployment |
The tool can be installed directly on the client system |
| A5 |
Cloud-Based Deployment |
The tool can be hosted and run by a cloud service provider (e.g.: AWS,
Azure, Google Cloud…). |
| A6 |
SaaS |
The tool can be offered as a service over internet connection |
| A7 |
Direct Deployment |
The entire simulaion software is installed and run on the machine to
test |
| A8 |
Containerized Deployment |
The tool can be deployed with a container solution like a docker image
|
| A9 |
Deployment Platforms* |
List of operating systems that support the tool deployment |
| A10 |
Target Platforms* |
List of operating systems, platforms and servers that can be the target of the tool's
attack simulation. |
| A11 |
Agent Based |
The tool supports an agent based approach for the simulation. An “agent”
is a software program that runs on the “victim” machine and connects back to the main software running the tool |
| A12 |
Agentless |
The tool doesn't require to install software on the machines that needs to be tested |
| A13 |
Virtual Agents |
The tool offers the possibility to create a "virtual agent" that
simulates a specific machine configuration in the system without actually deploying it |
| A14 |
Security Requirements |
The host of the software doesn't need to change its security requirements to install the
tool and run it. |
| A15 |
General Requirements |
The host of the software doesn't need other software or system modifications to install
the tool and run it. |
The Architecture category comprehends features describing the software technical components and
the deployment methodology. This section is crucial for deciding whether a specific solution suits a
particular use case. As previously mentioned, it is not generally recommended to exclusively verify
how many features a tool offers but rather to study which ones align with the user's needs. This
reasoning is particularly relevant to the features in this section. For instance, a tool that offers both
software as a service and on-premise solutions in a single package can be unnecessarily costly if the
buyer's system is not compatible with cloud environments.
Organization >
< Overview