Quick Start

To access the latest information about this topic and all Cloud Security releases, check out the Release Notes.

BMC Helix Cloud Security  is a SaaS (software-as-a-service) solution that enables you to quickly identify risks in your IT resources. The following table shows how you can quickly get started with using the solution.

The table includes links to walkthroughs that step you through the implementation flow.

Register for the service.

Create an account for Cloud Security and enable users to leverage that account (as necessary).


If you have an existing account, you must reset your password to accommodate the migration to a new security system.

Ensure that your environment meets the minimum system requirements.

The computer on which the connector is downloaded must have the following characteristics:

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

You can download and configure one or more of the out-of-the-box (OOB) connectors that are available in Cloud Security. See Onboarding.

To review 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 Cloud Security.

Run a scan on demand.

You can run a compliance scan by clicking directly and onboard AWS Cloud connector.

To run an on-demand scan:

  1. Choose Configure icon> Connectors.
  2. On the Manage Connectors page, locate the cursor on the connector for which you want to run compliance and click Evaluate Now button.

For more information about on-demand scanning and which connectors support this feature, see Managing connectors.

(On-premise only) Run the connector.

The next step is to run the on-premise 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.
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 Identifying violations and Managing resources.

To review an example of the process, see Walkthrough: Identifying CIS violations for AWS. In this example, In this scenario, 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. 

Remediate the violations.

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

To review 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.

(Optional) Navigate the Dashboard.You can go back and navigate the Dashboard for additional information, elements, or widgets to help with your assessments.
Free TrialYou can register for the 14-day free trial using this.

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