In my opinion, this is not such a good idea for several reasons:
1. Permission model for UCMDB is different from standard xNIX approach. There is no owner, group and others. It's based on user/roles. TomakeCIsinvisibleforsomeusers, multi-tenantneedtobeturnedon. Amountofmaintenance will raise significantly.
2. UCMDB has no option to hide attributes with asterisks. It's possible to hide some attributes from UI, but there is no point to do this if you'll consume this data some day.
3. You could find more details in "Roles Manager Page" in the HP Universal CMDB Administration Guide.
Thanks for your opinion. I pretty much also think that there is a heavy security backdoor with such a solution. Also there is logical issue that such information is not related to configuration management issues directly.
May be you can also promt to me if there is similiar functionality in CM of latest versions?