Managing notifications

BMC Helix Cloud Security offers features for creation of three types of notifications, namely, Reports, Incidents and Change.

Reports are created when the user wants to be notified when violations are detected and give periodic updates about violations at user-specified frequencies. Incidents give users control over the course of action that should be followed when violations are observed. Incidents are created when Cloud Security identifies violations and can be taken up or dismissed by the user depending on its threat level. Change give users further control when the violations is to be remediated. Change ticket is created in ITSM when user tries to create remediation action. The remediation will be completed only when it is approved by Remedy Administrator. 

You can configure report notifications/incidents/change under Configuration icon (Settings Icon.PNG) > Notifications, which supports the following features: 

Creating a Notification (Report / Incident/Change)

The following procedure is applicable to New Compliance Notification, Overall Summary, Create Incident and Create Change.


Steps

Example Screens

1.

Log on to BMC Helix Cloud Security and click Configure icon > Notifications.

image2019-8-15_2-54-44.png

2.

Click on Create Notification from the Manage Notifications page.

image2019-8-15_2-55-16.png

3.

On the popup screen that appears, select the type of notification desired from between New Violation Notification and Compliance Summary, Create Incident and Create Change (New Violation Notification has been chosen as an example for the purpose of this procedure).

Notofication.jpg

4.

On the Create a Notification screen, specify the required fields depending on the type of notification chosen:

On the Create a Notification screen, specify the required fields:

New Violation Notif.PNG

Field

Description

Name (required)

The name for the notification.

Notification Type (required)

The type of notification. Here, New Violation Notification.

Description (required)

The description for the notification. For example, a business requirement, or description about notification content.

Resources (required)

The connectors or tags which are required to create the notification.

Frequency (required)

The frequency of notification generation. This can be Daily, Weekly or Monthly. Time is defaulted to current browser time, rounded off to the nearest 30 minutes, and can also be set manually.

Time (required)

The time of notification generation. This is defaulted to current time zone and can be adjusted manually.

Email (required)

User can set this to self (email ID of logged in user) and/or check other to enter other email addresses to which the notification will be sent once generated.

On the Create a Notification screen, specify the required fields:

Overall Summary Notif.PNG

Field

Description

Name (required)

The name for the notification.

Notification Type (required)

The type of notification. Here, Compliance Summary.

Description (required)

The description for the notification. For example, a business requirement, or description about notification content.

Resources (required)

The connectors or tags which are required to create the notification.

Frequency (required)

The frequency of notification generation. This can be Daily, Weekly or Monthly. Time is defaulted to current browser time, rounded off to the nearest 30 minutes, and can also be set manually.

Time (required)

The time of notification generation. This is defaulted to current time zone and can be adjusted manually.

Email (required)

User can set this to self (email ID of logged in user) and/or check other to enter other email addresses to which the notification will be sent once generated.

On the Create a Notification screen, specify the required fields:

image2018-10-12_14-40-34.png

Field

Description

Name (required)

The name for the incident.

Notification Type (required)

The type of notification. Here, Create Incident.

Description (required)

The description for the incident. For example, a business requirement, or description about incident content.

Incident workflow (required)

Selection of TSO Instance, that is, the TSO connector required to create the incident.

Resources (required)

The connectors or tags which are required to create the incident.

Frequency (required)

The frequency of incident generation. This can be Daily, Weekly or Monthly. Time is defaulted to current browser time, rounded off to the nearest 30 minutes, and can also be set manually.

Time (required)

The time of incident generation. This is defaulted to current time zone and can be adjusted manually.

On the Create a Notification screen, specify the required fields:

image2019-1-10_20-50-30.png

Field

Description

Name (required)

The name for the Change.

Resources By(required)

The connectors or tags which are required to create the incident.

Create Change Request for (required)

The Change request can be for All Remediations, On-Demand Remediations and Auto Remediations.

BMC Helix Orchestration Instance (required)

Select the BMC Helix Orechestration Connector instance.

5.

Click Save.

Save Notif.PNG

6.

You will be apprised when the report/incident has been successfully created.

image2019-8-15_2-47-59.png

7.

Once the report/incident has been added to the Manage Notifications page, click on Run Now corresponding to the notification that needs to be generated. This ensures that the notification is generated on a subsequent schedule run and sent to the email address/addresses configured in the notification.

This step is optional and need be followed only if the user wants a notification generated immediately.

image2019-8-15_2-48-31.png

Notification created under a specific Organization is only applicable on the resource associated to the specific Organization. These notifications are only seen in context of the organization under which they are created.

Viewing / Updating a Report.

The following procedure is applicable to New Compliance Notification, Overall Summary.


Steps

Example Screens

1.

Log on to BMC Helix Cloud Security and click Configure icon > Notifications.

image2019-8-15_2-49-13.png

2.

On the Manage Notifications page, click on the link for the required notification under the Name column to view additional details for the selected notification.

image2019-8-15_2-49-36.png

3.

The Update a Notification page shows the name of the notification, description, frequency and time at which notification was generated, resources required for notification generation and email IDs to which the generated notification needs to be sent. Edit the required fields and click on Save to update details of the notification.

Updating 2nd.PNG

Deleting a Report


The following procedure is applicable to New Compliance Notification, Overall Summary.



Steps

Example Screens

1.

Log on to BMC Helix Cloud Security and click Configure icon > Notifications.

image2019-8-15_2-50-14.png

2.

On the Manage Notifications page, select the notification to be deleted and click on the Delete button.

image2018-9-11_16-40-57.png

3.

Click OK on the Delete Confirmation pop-up that appears.

Deletion 3.PNG

4.

You will be apprised when the notification has been successfully deleted.

image2019-8-15_2-51-42.png

Deleting a report/incident is a permanent action that cannot be undone.

Sample Notification Content

Below is a sample email for New Violation Notification sent to the email ID configured in the notification. You can also hover over the link in the mail to connect to Cloud Security UI. 

Email 1.PNG

Below is a sample email for Compliance Summary sent to the email ID configured in the notification. You can also hover over the link in the mail to connect to Cloud Security UI. 

Email 2.PNG

Incident IDs can be viewed under Violation Details page.

image2019-8-15_2-56-26.png

Change Ticket IDs can be viewed under Violation Details page as well as Remediation History Page.

image2019-1-10_21-11-52.png


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*