Getting Started

This topic was edited by a BMC Contributor and has not been approved.  More information.

BMC Helix Cloud Security is a SaaS (software-as-a-service) solution that enables you to quickly identify risks in your IT resources. This section helps you to get started with the product as it describes the overview, architecture, and end-to-end process flows for some of the commonly used features in BMC Helix Cloud Security. 

Quick start

This table provides an overview of the tasks that you need to perform to get started with BMC Helix Cloud Security.

Tasks

Documentation

Documentation 

1. 

Subscribe to a free trial.

You can subscribe to a 14 day free trial for BMC Helix Cloud Security.

Free Trial

2.

Ensure that your environment meets the minimum system requirements.

The computer on which any on-premises connector is downloaded must fulfill the following mininum requirements:

  • OpenJDK 11.0.2
  • 10 MB or more disk space to enable the logs to grow
  • Google Chrome browser

System requirements

3.

Onboard the connectors.

You can download and configure one or more of the out-of-the-box connectors that are available in BMC Helix Cloud Security.

To view an example of the process, see Walkthrough: Onboarding the AWS Cloud connector. In this example, a company has made a decision to monitor the compliance and security of their Amazon Web Services (AWS) accounts using BMC Helix Cloud Security.

Onboarding

4.

Run a scan on demand for a cloud connector.

By default, your environment is scanned at a scheduled time interval. To run a scan on demand, go to the Manage Connectors page and click Evaluate Now against a connector.

For example, if you have configured an AWS cloud connector, go to the connector and click Evaluate Now to view results on the dashboard.

Managing connectors

5.

(On-premises only) Run the connector.

Run any on-premises connector once you have downloaded the zip file.

Unzip the file, and do one of the following:

  • (Windows) Double-click run.bat to run the connector in your target environment.
  • (Linux) Execute the command chmod +x run.sh to grant execute permissions to the run.sh file. Then run the connector using the run.sh command.

Managing connectors

6.

Identify the resource violations.

Next, after setting up and running the connector, you can access the dashboard to manage the data. You can view the violations that are generated due to deviations from the rule evaluation criteria. You can aggregate the results by violation or by resource. See and .

To view an example of the process, see Walkthrough: Identifying CIS violations for AWS. In this example, a company is using Amazon Simple Storage Service (S3) to store and retrieve data. The company wants to use Cloud Security to ensure that the data in the buckets is properly secured. 

7.

Remediate the violations.

Finally, you want to identify and remediate the most critical violations.

To view an example of this process, see Walkthrough: Remediating compliance violations. This walkthrough topic shows you how to initiate a remediation action for a compliance violation with CIS policies for AWS.


Walkthroughs

For end-to-end process flows for commonly used features in BMC Helix Cloud Security, see Walkthroughs.

Key concepts

For understanding the architecture and the terms used throughout this documentation, see Key concepts

Was this page helpful? Yes No Submitting... Thank you

Comments