Thanks Justin, this is a great example of how we can leverage ServiceNow for customer offboarding and data destruction certification... I'll share this with a few folks on my team. Cheers!
You video came at a good time. I was looking for information on how to secure data, such as PII, financial, and other data away from other parts of the company. Thought of using ACL's for CRUD operations. However, this seems to be an easier way to manage that data. It might require a data policy as well as an ACL along with what you have mentioned here. Do you have any videos that detail how to protect this data from System Administrators and making it only available to people such as Human Resource Managers, Financial Managers, etc?
Hey Kevin - thank you for watching! I don't have any videos on that specifically but you're on the right track with ACLs. I recommend looking more into ACLs and encryption features. The other thing to consider is what are the auditability requirements for who has accessed (even just read) that data and why. Requiring a user to log why they accessed certain data elements and logging it has been a use case I've seen in my previous roles. In this video the Information Objects are meant to "represent" (think avatar) the types of data so that you can associate them with configuration items in the CMDB. I wouldn't recommend storing ANY sensitive data with these or the CMDB. All sensitive data should be protected with ACLs, roles, encryption and soon, with Tokyo, you'll hear about a new capability that can help in this space as well. I'll try to think of a way to make a video out of this - I feel like this could be a good explainer that might be helpful you and others.
Thanks Justin, this is a great example of how we can leverage ServiceNow for customer offboarding and data destruction certification... I'll share this with a few folks on my team. Cheers!
Awesome - thanks for watching Ash!
You video came at a good time. I was looking for information on how to secure data, such as PII, financial, and other data away from other parts of the company. Thought of using ACL's for CRUD operations. However, this seems to be an easier way to manage that data. It might require a data policy as well as an ACL along with what you have mentioned here. Do you have any videos that detail how to protect this data from System Administrators and making it only available to people such as Human Resource Managers, Financial Managers, etc?
Hey Kevin - thank you for watching! I don't have any videos on that specifically but you're on the right track with ACLs. I recommend looking more into ACLs and encryption features. The other thing to consider is what are the auditability requirements for who has accessed (even just read) that data and why. Requiring a user to log why they accessed certain data elements and logging it has been a use case I've seen in my previous roles. In this video the Information Objects are meant to "represent" (think avatar) the types of data so that you can associate them with configuration items in the CMDB. I wouldn't recommend storing ANY sensitive data with these or the CMDB. All sensitive data should be protected with ACLs, roles, encryption and soon, with Tokyo, you'll hear about a new capability that can help in this space as well. I'll try to think of a way to make a video out of this - I feel like this could be a good explainer that might be helpful you and others.