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 () > Notifications, which supports the following features: 

Creating a Notification (Report / Incident/Change)

	Steps	Example Screens
1.	Log on to BMC Helix Cloud Security and click Configure icon > Notifications.
2.	Click on Create Notification from the Manage Notifications page.
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).
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: 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: 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: 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: 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. Additional Information on Resources Resources for New Violation Notification and Compliance Summary include connectors and tags, and can be chosen manually. Either All Connectors can be assigned or Selected Connectors will enable connectors specified by user. Either All Tags can be assigned or Selected Tags will enable tags specified by user.
5.	Click Save.
6.	You will be apprised when the report/incident has been successfully created.
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.

Viewing / Updating a Report.

Deleting a Report

Sample Notification Content