D
DiscoverSoft
I'm rather new to encryption issues, but have a project for a federal agency
that requires certain privacy fields to be encrypted. They can't use SQL
server for this project. It's a typical MS Access frontend app/backend
dataset split.
I've been told the requirements for privacy encryption are as follows:
'It should be FIPPS 140-2 compliant or triple AES'
I've used the CryptoSys API by DI Managment in AU for other projects, but
not sure that it conforms to the above spec. Does anyone know a toolkit or
method to use that will ensure I'm compliant with this encryption? Would the
Microsoft.Crypto API help me here? If so, any examples?
These folks are still on XP machines, using Office 2003. Any help would be
greatly appreciated.
Thanks,
Tod Hardin
that requires certain privacy fields to be encrypted. They can't use SQL
server for this project. It's a typical MS Access frontend app/backend
dataset split.
I've been told the requirements for privacy encryption are as follows:
'It should be FIPPS 140-2 compliant or triple AES'
I've used the CryptoSys API by DI Managment in AU for other projects, but
not sure that it conforms to the above spec. Does anyone know a toolkit or
method to use that will ensure I'm compliant with this encryption? Would the
Microsoft.Crypto API help me here? If so, any examples?
These folks are still on XP machines, using Office 2003. Any help would be
greatly appreciated.
Thanks,
Tod Hardin