It would be great to set a property on a field in a feature class/table as "sensitive", i.e. the field contains sensitive information.
We have good overview over which fields in each feature class/table contain sensitive information and have routines in place on database/Desktop level. As soon as it comes to published services, it is easy to loose track. Often, a feature class is part of a number of published services and one has to remember to turn off the field in the properties before publishing. We have of course forgotten to turn off certain fields and shared the item with more people in Portal and ArcGIS Online as necessary, leading to data leakage.
It would be much easier to get a warning when publishing the service, informing the user that fields marked as sensitive are visible in the service. Also, post publishing, we could run script, that spits out if the property of a field within a service that is "sensitive". The property would show up in the REST page of the item, see attachment.
