Search results for query: *

Thanks for the feedback.

Anyone running Nod32 on an Aloha system? Just want to make sure there are no known issues. I'm sooo ready to dump Norton.

A simple text search can find unencrypted card numbers, if they exist. You don't have to know anything about aloha, file names/types, etc. I will provide more details when I can.

It's true, even the card processors are confused. But they will have no problem passing the buck and fining the heck out of you. PCI . . . enjoy https://www.pcisecuritystandards.org/docs/pci_audit_procedures_v1-1.doc https://www.pcisecuritystandards.org/pdfs/pci_dss_v1-1.pdf...

Yes. We found out about the PCI rules the hard way. Even our vendor isn't aware of all the rules.

Is this fixlog tool something I can get my hands on? Or is it some sort of vendor-only program?

I can read my trans.log files (at least the ones created by aloha version5) with Textpad. Not the entire file, but I can see card numbers and expiration dates. Translogs created with version 5.3.26 are completely encrypted and unreadable when I try the same Textpad method. I was also told that...

According to the vendor, Deltrack only works to sanitize .stl (settle) files. They ran it multiple times, but it left many .stl files unchanged. Finally, we just deleted them. They also say that "regrinding the data" is what updates the trans.log files (which also contain card data). After...

Any tips on cleaning card data from older Aloha files? Regrinding data still leaves behind some plain text card numbers in translog. I'm hoping for something more elegant than my plan of a search-and-replace with text editor.