Add "Protection needs" to CIs and allow to inherit them up/down

Idea ID 2770369

Add "Protection needs" to CIs and allow to inherit them up/down

Many of our german banking customers are required to manage protection levels with their servers/apps etc.

And if multiple protection levels are found within one Service structure, the whole service structure must be set to the highest protection level. The highest level would then have to be applied to all upstream CIs.

I have no clear vision how that could be implemented, but we have one customer who realised their needs in UCMDB using enrichments.

Their "Information Security Level" was made of four values:
Confidentiality, Integrity, Authenticity, availability.
These were visualised on the CI label of their new CIT "Information Security Level", see attached JPG.

Having this as a standard element in UCMDB would be a USP too.

 

 

3 Comments
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

I would say this functionality should be achievable with enrichment and the information security level CI, and it would be worth sharing an example on how this could be implemented - but I would be careful having it OOTB, as not all customers have the same rules. This subject also touches service modeling and impact analysis.

So the use case is definitely valid, and worth working on the use case both for an actual implementation of the propagation enrichment (I could see some limitations on the max-rule, you mention), how to visualize on the service the different information security levels etc.

Micro Focus Expert
Micro Focus Expert
Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.