Home
Security Compliance Analytics
Security and Compliance Analytics (SCA) is a web-based application designed to help you manage security, vulnerability, and risk assessment. The application archives security and vulnerability compliance check results to identify configuration issues and report levels of compliance toward security configuration goals.
Security and Compliance Analytics User Guide
BigFix for Security and Compliance Analytics (SCA) is a web-based application that is designed to help you manage security, vulnerability, and risk assessment. The application archives security and vulnerability compliance check results to identify configuration issues and report levels of compliance toward security configuration goals.
Working with patch reports
System requirements
Configure your BigFix Patch Reporting deployment environment according to the following requirements.

Security Compliance Analytics
Security and Compliance Analytics (SCA) is a web-based application designed to help you manage security, vulnerability, and risk assessment. The application archives security and vulnerability compliance check results to identify configuration issues and report levels of compliance toward security configuration goals.
- Security and Compliance Analytics Setup Guide
  BigFix for Security and Compliance Analytics (SCA) is a web-based application designed to help manage security, vulnerability, and risk assessment. The application archives security and vulnerability compliance check results to identify configuration issues and report levels of compliance toward security configuration goals.
- Security and Compliance Analytics User Guide
  BigFix for Security and Compliance Analytics (SCA) is a web-based application that is designed to help you manage security, vulnerability, and risk assessment. The application archives security and vulnerability compliance check results to identify configuration issues and report levels of compliance toward security configuration goals.
  - Introduction
  - Viewing deployment compliance status reports
    You can view the compliance status in your deployment from any of the four report types.
  - Working with patch reports
    - Enabling patch reporting
      You can enable or disable patch reporting.
    - Report types
    - Saved reports
    - Managing reports
      You can generate and manage the patch reports by using the following actions in the application.
    - Enabling mail settings
      You must configure outbound email in mail settings to schedule an export to an email recipient. The patch report can be sent to multiple email recipients.
    - Adding external sites
      You can add external sites that are not included in the supported sites list.
    - System requirements
      Configure your BigFix Patch Reporting deployment environment according to the following requirements.
    - Sample use cases
  - Management Tasks
  - Configuring report definitions using REST API
    Administrators can use REST API to create, update, and delete saved report view definitions across TEMA instances.
  - Disaster Recovery for BigFix Compliance Analytics
    Use the standard cold standby method of creating a backup and restoring the system in your disaster recovery plan for BigFix Compliance Analytics.
  - Example Reports - Compliance
    View examples of the various BigFix Compliance Analytics reports.
  - Example reports - Patch reports
    View examples of the various BigFix Compliance Patch reports.

System requirements

Configure your BigFix Patch Reporting deployment environment according to the following requirements.

Table 1. Supported components and system requirements to deploy BigFix Patch Reporting
Disk space requirements with and without the SCA patch domain enabled.
Components	Requirements
Disk space requirements for data base tables (patch domain)	SCA without patch domain enabled: 100,000 endpoints, 100 subscribed checklists, and 12 computer groups SCA with patch domain enabled: 100,000 endpoints, 100 subscribed check lists, 30 subscribed patch sites, and 12 computer groups
Disk space for the tem_analytics database	Data file size: Initial ETL report SQLServer MDF: 54.7 GB, LDF 108.4 GB, TempDB: 8x1.4 GB each Data file size: Incremental ETL import after patch enabled SQLServer MDF: 57.9 GB, LDF: 108.5 GB, TempDB: 8x1.4 GB each
JVM heap size 2GB	2 GB heapsize in `jvm.options` 2 GB for SCA 1.10

Table 2. Supported components and system requirements to deploy BigFix Patch Reporting
Windows server versions for SCA Compliance and Patch Domains.
Components	Requirements
Minimum - Windows Server 2008 R2	SP1, 16 GB RAM 32 GB for best results
Maximum: Windows Server 2016 R2	SP2, 16 GB RAM 32 GB for best results
MSQL Server 2008 R2	SP3, 16 GB RAM 32 GB for best results
MSQL Server 2016 R2	SP3, 16 GB RAM 32 GB for best results

Recommendations:

The Windows SCA Compliance service runs on the Windows server needs sufficient free memory (RAM) to efficiently complete ETL. The default size for the SCA Compliance Service is 2GB.
For Windows servers with small amounts of RAM ensure a minimum 3 GB free space at all times during each ETL import process and an extra 1GB for the overhead of Java.
For Windows server with plenty of RAM, and large deployments, the JVM heap size limit can be increased to 4GB to improve ETL import times. To change the JVM heap size limit, change the setting "-Xmx2048m" to "-Xmx4096m" in the file JVM.options file in the directory. The file is located in C:\Program Files\HCL\SCA\wlp\usr\servers\server1\jvm.options. In order for the changes to take effect, you must restart the Compliance Service.