Video Screencast Help

Solution Pack Recommendation?

Created: 14 Mar 2013 • Updated: 15 Mar 2013 | 4 comments
This issue has been solved. See solution.

To start out, we only want to monitor and report in US Social Security numbers, dates of birth, credit card numbers and a proprietary card number that is similar to a credit card number, but not the same.  In the future, we may want to monitor a few other things such as source code.

We will be uncertain if we will ever have a very large list of things to monitor and eventually block until after we have reports on where the data is going now and then educate users on correct ways to transfer the data.

Should we use the General pack or High Tech or something else?

Is it best to pick a solution pack with lots of rules and disable everything we don't want to use or choose one with few rules?

Operating Systems:

Comments 4 CommentsJump to latest comment

stumunro's picture

Net,

If you want it for the response rules go ahead.... there are pre canned SSN, PCI templated for thiose policies. Under the propietary card numbers if you have a db create a data source as a xls file and then create a EDM rule for those as it can updated daily if needed.

 

you can always delete/disable the policies you dont use. you may also want to look @ the financial sector solutin pack for this. let me knwo if you have any  more questions.

SOLUTION
NetUser's picture

Is there a solution pack that also can detect state benefit card numbers in the same automated manner as credit card numbers are detected such as cards like these?

 

We would not have all these numbers in our own database, so there is no way to do exact matches against an Excel file.

stumunro's picture

if you know what the digits start with, you can write a regex value against the card...