ASSESS WORKLOADIMPACT IN REAL-LIFE
ENVIRONMENTS.
TEST TO SAVE
Estimated Cost of Security Overhead
Cloud spend continues to increase dramatically, with the cloud computing market expecting to pass $1 trillion by 2028. For enterprises, in 2023 this is translating to a $33 million cloud spend annually. However, while these costs are dramatic, there are still a lot of unknowns as to how spend is being allocated. In fact according to The State of Cloud Cost Intelligence, 60% of respondents said their cloud costs were too high, while only 30% of respondents knew where their cloud costs were going.
To help address cloud costs, consider the security products you use. Aside from providing less-than-ideal security in many instances, we’ve found that many legacy security tools can take from 20%-35% overhead on a machine! For enterprises, this can translate to more than $6M-$11M annually. Running SecurityPerf can help you make sure you are making informed economic decisions when selecting a security solution.
HOW IT WORKS
Two systems utilize containers for real-world benchmarking.

TECH SPECS
SecurityPerf Machine 1 (Client) Requirements
OS
Linux, kernel v3.5 or higher. Distribution agnostic.
Processor
x86-64, ARM-64
Memory
1GB
Disk Space
10mb + results space, approximately 100mb under average use
Installation Reqs.
- Python
- The latest version of Docker engine installed.
- The user that is running run.py must be able to run Docker commands without requiring root access.
SecurityPerf Machine 2 (Server) Requirements
OS
Linux, kernel v3.5 or higher. Distribution agnostic.
Processor
x86-64, ARM-64
Memory
Up to 8GB, depending on workload(s) and security products being evaluated
Disk Space
Up to 1GB, depending on workload(s)/container(s) and security products being evaluated
Installation Reqs.
- An SSH server with password-based login enabled.
- The latest version of Docker engine installed.
- The user that is running run.py must be able to run Docker commands without requiring root access.
- You cannot run any services on this system with ports that conflict with the services being tested. The services being tested use their default ports. For example, apache uses port 80.