Sensitive data issue

Hi, we have an issue with people’s dates of birth being on documents stored in our people directory.

Currently there are two fields (one date and one text) that store the DOB in different formats, both these fields have their information imported via a Notrix Import job.

The problem has come to light because people using the web based search were putting in years (i.e. 1970) and determining that the records returned were people born in that year. There is also the problem that people can just go into notes and look at the document properties of selected individuals documents.

Our situation is further clouded by the fact that a second database uses the DOB as a very basic web validation tool (we know this isn’t very secure but it is good enough for its purpose).

So to conclude we need this:

The birthdate data to be on the records in Notes so that our ‘people finder’ database can look it up using an @DbLookup formula but to be hidden from people looking at the document properties and hidden from the search (the search is the ‘VSearch?SearchView&Query’ type of search).

I am thinking encryption but have never used it before does it seem to like a good avenue to explore ?

Many Thanks

Paul

Subject: sensitive data issue

The issue that normally creates a problem for encryption is that only those with the encryption key can edit the documents that have an encrypted field. That could be a show-stopper straight off. If not it would be worth looking at, not used it in anger myself for the reason stated.

The other way is of course to store the dob in a separate document, with readers fields. This causes a problem for your search maybe though. For display purposes you could have a computed for display field in a form, with a dblookup which would fail of course for those people that don’t have access to the dob document.