CODEWITHSUNDEEP
securityc++-clierasure
user3511585
user3511585

Reputation: 41

gcnew and secure erasure

I have memory that I have to allocate with gcnew (C++, passing the memory to managed code), which will contain secure information (passwords, HIPAA data, etc.). I realize that such memory is garbage collected, and that implies that I don't control when it is deallocated. But that wouldn't be a problem if there was a way to guarantee it got securely wiped before I turn loose of it.

Is there a way to guarantee gcnew'd memory is securely erased? In my particular case, I'm gcnew'ing String objects, but a general approach would be even better.

Upvotes: 0

Views: 64

Answers (1)

Johanns Gregorian
Johanns Gregorian

Reputation: 156

There isn't an elegant solution to the problem. But, this should be a non-issue/concern if the system running your code is properly secured in accordance to HIPPA.

You may also want to try SecureString instead of String:

SecureString: MSDN

CodeProject tutorial

Upvotes: 2

Related Questions