Microsoft Default Credit Card Number is not working effectively.
Hi All, I just observe that Microsoft default SIT for Credit Card is detecting more False Positives, it is detecting the 16 digit transaction numbers, tracking ID's, Receipt numbers and even Microsoft support ticket numbers also detecting as Credit Card Numbers. how can we finetune the Microsoft Default SIT to make sure it should detect only valid Credit Card Numbers.
Disease Sensitive Information Type Unusable (SIT) in MI, Need Term Exclusions
My organization is based in Michigan and MI is being flagged in both All Medical Terms and Conditions as well as Diseases (since the former contains the latter). I assume it is associating MI with the abbreviation for myocardial infarction. The majority of our documents have the MI state abbreviation. Diseases is a very important SIT to us since we are a public health organization. It catches a lot of terms that are not found by the ICD-9 and ICD-10 SIT dictionaries. I cannot copy the Disease SIT within Purview to create my own (the option is greyed out since it is an "enhanced classifier" and I haven't been able to access it or export via PowerShell. I have tried creating a custom sensitive info type and Diseases is not an available option to use as a foundation. I would assume it could be found in the Keyword List or Dictionary options, but it isn't present. I really don't have a good starting point for creating my own version of Diseases. Any suggestions would be greatly appreciated. Ideally Purview would allow organizations to use its curated list of SIT options and over-ride them within the SIT or as each SIT is applied within a policy. That way the SIT would be kept current by Microsoft and the exceptions could be applied independently. Updates to the SIT dictionary would then have less impact vs. missing updates by creating a copy for your organization.
Export Microsoft Purview SIT results
Hello there! Some time ago, I introduced my partner to Microsoft Purview's sensitive information types. We have been working hard to refine its results by double-checking the false positives. I am now seeking a way to export the results, specifically the number of sensitive information types found per Microsoft Teams, SharePoint, and other platforms. Is there an easy way to do this? While I am able to make an export within the Purview Center, it is very basic and requires me to stitch Excel sheets together. Could someone point me towards useful documentation/ information? Thank you in advance for your help!Built-in SSN sensitive info type - excluded values
Does Microsoft's built-in SSN sensitive info type exclude any values by default or do we need to customize it to remove potential false positives for scenarios like the following: SSNs beginning with the number "666" in positions 1-3 SSNs beginning with the number "9" SSNs beginning with the number "000" in positions 1-3 SSNs with the numbers "00" in positions 4-5 SSNs with the number "0000" in positions 6-9 SSNs with repeating values. All 1's, 2's, 3's, etc. SSNs in a predictable sequence; 123456789 or 987654321
