Common use of Security Resources Clause in Contracts

Security Resources. A Security Resource is a commonly used security agent that the Experimenter can include in her experiment. She can access and configure it through a static initial configuration, included in the TOSCA description of the Resource, or, once deployed, through a REST interface that exposes its main services. The Experimenter can also ask the Security Resource to send its log messages to a remote log collector, which makes them available in a simple web page reserved to her. The Experimenter could easily access it through its web browser and check the behaviour of her all security agents, and to see some statistics. The Experimenter can get the Security Resource in two different formats:  As an agent directly installed in the VM that she wants to monitor. The system will provide her a script that the Experimenter has just to run inside the VM. It will be already configured as required in the TOSCA description of the resource. The output of the script will provide to the Experimenter information on how to access the deployed resource (URLs, etc.)  As a standalone VM the Security Resource will be deployed directly by the Security Manager in the testbed chosen by the Experimenter. The Security Manager will take care of the initial configuration of the resource. The Experimenter has to set up on her own the redirection of the network traffic that she wants to control through the Security Resource VM (by means of tunnelling or SDN capabilities). To date the only Security Resource available on the SoftFIRE environment is the firewall.

Security Resources. A Security Resource is a commonly used security agent that the Experimenter can include in her experiment. She can access and configure it through a static initial configuration, included in the TOSCA description of the Resource, or, once deployed, through a REST interface that exposes its main services. The Experimenter can also ask the Security Resource to send its log messages to a remote log collector, which makes them available in a simple web page reserved to her. The Experimenter could easily access it through its web browser and check the behaviour of her all security agents, and to see some statistics. The Experimenter can get the Security Resource in two different formats:  • As an agent directly installed in the VM that she wants to monitor. The system will provide her a script that the Experimenter has just to run inside the VM. It will be already configured as required in the TOSCA description of the resource. The output of the script will provide to the Experimenter information on how to access the deployed resource (URLs, etc.)  • As a standalone VM the Security Resource will be deployed directly by the Security Manager in the testbed chosen by the Experimenter. The Security Manager will take care of the initial configuration of the resource. The Experimenter has to set up on her own the redirection of the network traffic that she wants to control through the Security Resource VM (by means of tunnelling or SDN capabilities). To date the only Security Resource available on the SoftFIRE environment is the firewall.