Watermarking based on sensitivity labels misses the point - feature request

%3CLINGO-SUB%20id%3D%22lingo-sub-2673701%22%20slang%3D%22en-US%22%3EWatermarking%20based%20on%20sensitivity%20labels%20misses%20the%20point%20-%20feature%20request%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2673701%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3Ein%20the%20past%20I've%20used%20other%20RMS%20products%2C%20primarily%20focused%20on%20PDF%20content%20(yes%2C%20Adobe%20RMS%20and%20others)%20and%20the%20primary%20driver%20for%20watermarking%20RMS%20content%20is%20to%20determine%20the%20source%20of%20the%20leak%20and%20when%20it%20happened.%26nbsp%3B%20So%20watermarks%20have%20the%20username%20of%20the%20person%20viewing%20the%20document%20and%20the%20time%20at%20which%20they%20were%20viewing%20it%20-%20so%20any%20screenshots%2Fprintouts%2Fphotos%2Fetc%20identify%20who%20was%20looking%20at%20the%20document%20and%20when.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20Microsoft's%20dynamic%20watermarking%20using%20variables%2C%20is%20only%20able%20to%20determine%20the%20username%20and%20time%20when%20the%20labelling%20occurred.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoesn't%20this%20miss%20the%20point%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20I%20please%20request%20the%20ability%20to%20dynamically%20watermark%20at%20VIEW%20time%2C%20so%20that%20we%20can%20determine%20who%20is%20leaking%20content.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ECraig%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2673701%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Information%20Protection%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ERights%20Management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2674175%22%20slang%3D%22en-US%22%3ERe%3A%20Watermarking%20based%20on%20sensitivity%20labels%20misses%20the%20point%20-%20feature%20request%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2674175%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F559746%22%20target%3D%22_blank%22%3E%40CraigHumphrey%3C%2FA%3E%26nbsp%3BThis%20is%20indeed%20the%20case%2C%20and%20your%20suggestion%20to%20also%20add%2Fmodify%20the%20watermark%20based%20on%20viewing%20a%20document%20is%20a%20good%20one%20IMHO.%20I%20don't%20know%20if%20it%20can%20be%20easily%20implemented%20by%20Microsoft%20though%2C%20as%20I%20expect%20that%20the%20application%20used%20to%20view%20such%20files%20will%20need%20to%20support%20the%20content%20marking%2Fwatermark%20feature%20of%20MIP.%20You%20can%20however%20raise%20a%20feature%20request%20for%20MIP%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FMIP%2FFeatureRequest%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20if%20you'd%20like%20to%20see%20if%20Microsoft%20has%20any%20thoughts%20on%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2681525%22%20slang%3D%22en-US%22%3ERe%3A%20Watermarking%20based%20on%20sensitivity%20labels%20misses%20the%20point%20-%20feature%20request%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2681525%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F960791%22%20target%3D%22_blank%22%3E%40pvanberlo%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft's%20own%20documentation%20pointed%20me%20here%20to%20make%20feature%20requests%20(since%20UserVoice%20is%20dying)%2C%20so%20thanks%20for%20the%20link.%26nbsp%3B%20I'll%20see%20what%20happens.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

in the past I've used other RMS products, primarily focused on PDF content (yes, Adobe RMS and others) and the primary driver for watermarking RMS content is to determine the source of the leak and when it happened.  So watermarks have the username of the person viewing the document and the time at which they were viewing it - so any screenshots/printouts/photos/etc identify who was looking at the document and when.

 

However, Microsoft's dynamic watermarking using variables, is only able to determine the username and time when the labelling occurred.

 

Doesn't this miss the point?

 

Can I please request the ability to dynamically watermark at VIEW time, so that we can determine who is leaking content.

 

Thanks

Craig

2 Replies

@CraigHumphrey This is indeed the case, and your suggestion to also add/modify the watermark based on viewing a document is a good one IMHO. I don't know if it can be easily implemented by Microsoft though, as I expect that the application used to view such files will need to support the content marking/watermark feature of MIP. You can however raise a feature request for MIP here if you'd like to see if Microsoft has any thoughts on this.

Thanks @pvanberlo,

 

Microsoft's own documentation pointed me here to make feature requests (since UserVoice is dying), so thanks for the link.  I'll see what happens.