System Requirements for Virtual Appliances
To ensure that JSA works correctly, you must use virtual appliances that meet the minimum requirements.
For more information about supported hypervisors and virtual hardware versions, see Creating Your Virtual Machine.
JSA Console only: JSA virtual appliances require x86 hardware.
JSA Console only: JSA appliances are certified to support certain maximum events per second (EPS) rates. Maximum EPS depends on the type of data that is processed, system configuration, and system load.
The minimum requirements support JSA functions with minimum data sets and performance. The minimum requirements support a JSA system that uses only the default apps. For optimal performance, use the suggested requirements.
You can change the memory or the CPU of your virtual appliance by shutting down the virtual appliance and making the changes. When you restart the virtual appliance, the system detects the changes and adjusts the performance-related configuration.
Memory Requirements
The following table describes the memory requirements for virtual appliances.
Appliance |
Minimum memory requirement |
Suggested memory requirement |
---|---|---|
JSA Flow Processor Virtual 1299 |
6 GB |
6 GB |
JSA Event Collector Virtual 1599 |
12 GB (up to 20,000 EPS) 64 GB (40,000 EPS) 128 GB (80,000 EPS) |
16 GB (up to 20,000 EPS) 64 GB (40,000 EPS) 128 GB (80,000 EPS) |
JSA Event Processor Virtual 1699 up to 20,000 EPS |
JSA Console only: 16 GB FIPS mode only: 12 GB |
JSA Console only: 64 GB FIPS mode only: 48 GB |
JSA Event Processor Virtual 1699 20,000 EPS or higher |
128 GB |
128 GB |
JSA Flow Processor Virtual 1799 up to 1,200,000 FPM |
16 GB |
64 GB |
JSA Flow Processor Virtual 1799 1,200,000 FPM or higher |
128 GB |
128 GB |
JSA Threat Analytics “All-in-one” or Console 3199 5,000 EPS or less 200,000 FPM or less |
32 GB |
64 GB |
JSA Threat Analytics “All-in-one” or Console 3199 30,000 EPS or less 1,000,000 FPM or less |
128 GB |
128 GB |
JSA Log Manager Virtual 8099 |
24 GB |
48 GB |
JSA Risk Manager 700 |
24 GB |
48 GB |
JSA Vulnerability Manager Processor 600 Note:
The JSA Vulnerability Manager scanner is end of life (EOL) in 7.5.0 Update Package 6, and is no longer supported in any version of JSA. In JSA 7.5.0 Update Package 6 and later, you can continue to use thirdparty scanners with your JSA Vulnerability Manager platform, but you cannot scan within your DMZ.
|
32 GB |
32 GB |
JSA Vulnerability Manager Scanner 610 Note:
The JSA Vulnerability Manager scanner is end of life (EOL) in 7.5.0 Update Package 6, and is no longer supported in any version of JSA. In JSA 7.5.0 Update Package 6 and later, you can continue to use thirdparty scanners with your JSA Vulnerability Manager platform, but you cannot scan within your DMZ. |
16 GB |
16 GB |
JSA App Host 4000 |
12 GB |
64 GB or more for a medium sized App Host 128 GB or more for a large sized App Host |
Processor requirements
The following table describes the CPU requirements for virtual appliances.
Appliance |
Threshold |
Minimum number of CPU cores |
Suggested number of CPU cores |
---|---|---|---|
JSA Flow Processor 1299 |
10,000 FPM or less |
4 |
4 |
JSA Event Collector Virtual 1599 |
5,000 EPS or less |
8 |
16 |
20,000 EPS or less 40,000 EPS or less 80,000 EPS or less |
19 40 80 |
19 40 80 |
|
JSA Event Processor Virtual 1699 |
5,000 EPS or less |
8 |
24 |
20,000 EPS or less |
16 |
32 |
|
40,000 EPS or less |
40 |
48 |
|
80,000 EPS or less |
56 |
JSA Console only: 80 FIPS mode only: 56 |
|
JSA Flow Processor Virtual 1799 |
150,000 FPM or less |
4 |
24 |
300,000 FPM or less |
8 |
24 |
|
1,200,000 FPM or less |
16 |
JSA Console only: 32 FIPS mode only: 24 |
|
2,400,000 FPM or less |
JSA Console only: 40 FIPS mode only: 48 |
48 |
|
3,600,000 FPM or less |
56 |
80 |
|
JSA Threat Analytics “All-in-one” or Console 3199 |
25,000 Flows per minute (FPM) or less 500 EPS or less |
4 |
24 |
50,000 FPM or less 1,000 EPS or less |
8 |
24 |
|
100,000 FPM or less 1,000 EPS or less |
12 |
24 |
|
200,000 FPM or less 5,000 EPS or less |
16 |
32 |
|
300,000 FPM or less 15,000 EPS or less |
40 |
48 |
|
1,200,000 FPM or less 30,000 EPS or less |
56 |
80 |
|
JSA Log Manager Virtual 8099 |
2,500 EPS or less |
4 |
16 |
5,000 EPS or less |
8 |
16 |
|
JSA Vulnerability Manager Processor 600 Note:
The JSA Vulnerability Manager scanner is end of life (EOL) in 7.5.0 Update Package 6, and is no longer supported in any version of JSA. In JSA 7.5.0 Update Package 6 and later, you can continue to use thirdparty scanners with your JSA Vulnerability Manager platform, but you cannot scan within your DMZ. |
4 |
4 |
|
JSA Vulnerability Manager Scanner
610 Note:
The JSA Vulnerability Manager scanner is end of life (EOL) in 7.5.0 Update Package 6, and is no longer supported in any version of JSA. In JSA 7.5.0 Update Package 6 and later, you can continue to use thirdparty scanners with your JSA Vulnerability Manager platform, but you cannot scan within your DMZ. |
4 |
4 |
|
JSA Risk Manager 700 |
8 |
8 |
|
JSA App Host 4000 |
4 |
12 or more for a medium-sized App Host 24 or more for a large-sized App Host |
Storage Requirements
Your virtual appliance must have at least 256 GB of storage available.
The following table shows the storage requirements for virtual installations.
System classification |
IOPS |
Data transfer rate (MB/s) |
---|---|---|
Minimum performance |
800 |
500 |
Medium performance |
1200 |
1000 |
High Performance |
10,000 |
2000 |
Small All-in-One (Console) or 1699 |
300 | 300 |
Event/Flow Processors | 300 | 300 |
A software installation is a JSA installation on your hardware that uses a RHEL operating system that you provide. You must configure partitions and complete other RHEL preparation before a JSA software installation.