| QUOTE REQUEST | CONTACT |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
FOR MORE INFO
|
||||
|
Q: Is it illegal (SOX or other) to have audit columns (last updated by, etc.) on the same database record row as the data itself? A: No, this is very typical. Most records are stamped with the user ID and date/time. You just need to have the right security or architecture (i.e., updates only through views or stored procedures) to prevent updates to these fields.
Previously submitted questions and answers: Q: Is this just another data security product
A: No. Until recently, data protection has focused on perimeter-based security efforts – “preventing the outsiders from getting in.” The growing threat involves insiders; insiders that commit fraud or unknowingly make errors that jeopardize data assets. And of those insiders, privileged users – especially DBAs and others with direct access to information assets – can be the biggest concern. Some regulations (including the Sarbanes-Oxley Act) now require that privileged users be monitored. Lumigent Audit DB is the only data auditing solution that provides an irrefutable audit of privileged user access because it’s the only solution that audits activity at the source of access – at the database layer. Audit DB provides segregation of duties so that users being audited cannot “turn off” the audit trail; nor can it be circumvented – elements required by strict auditing requirements not provided by other solutions. The best security defense is a “defense-in-depth”. While perimeter security efforts are a necessary component, solutions like Audit DB that monitor activity inside the firewall are critical.
In addition to improved security, Audit DB helps monitor overall policies and controls for effectiveness and identifies violations. With Audit DB, organizations can easily understand which security policies and controls are working – and which are not.
|
||||