| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 3353 |
| Technical Name |
audit_security_sentinel |
| License | OPL-1 |
| Website | https://neurodev.cl |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 3353 |
| Technical Name |
audit_security_sentinel |
| License | OPL-1 |
| Website | https://neurodev.cl |
| Versions | 17.0 18.0 19.0 |
|
⚡ MAY 2026 LAUNCH PROMO ⚡
USD $249
USD $159
(-36%)
Limited launch pricing · Valid until May 31, 2026
Buy now and lock the discount — price returns to USD $249 on June 1.
|
Security Sentinel
If someone touched your data, the log remembers. And nobody can erase it.
Forensic-grade audit trail of every change in your Odoo, sealed with SHA-256. Who, when, from which IP, value before and value after. Tamper-proof. Built for audits and compliance.
Why your Odoo is vulnerable today
0
Immutable logs in native Odoo. Default logging can be modified or disabled. There is no way to prove the record was not altered.
12 months
Average time to detect internal fraud in companies without forensic audit logs (IBM Cost of a Data Breach 2024). Late detection means damage done.
2 years
Minimum retention required by ISO 27001, GDPR, SOX and most modern cybersecurity laws. Without forensic logs, no proof of compliance.
What it catches — real scenarios
Every CREATE, WRITE and DELETE on the models you select, logged with who, when, from which IP, value before and value after. Typical examples:
| CRITICAL | Approved invoice deleted: "A validated invoice was deleted by a user with elevated permissions on Friday at 18:30" |
| HIGH | Suspicious price change: "A product's price was modified 5 times in 2 hours from 3 different IP addresses" |
| HIGH | Closed journal entry modified: "A closed accounting entry was modified 30 days after its creation date" |
| CRITICAL | After-hours access: "Login at 03:42 from unusual IP with modification of vendor banking data" |
| MEDIUM | Mass change: "A user modified 47 customer records in less than 10 minutes" |
| HIGH | Critical attachments deleted: "Documents attached to a purchase order were deleted after goods receipt" |
You decide which models to monitor: invoices, journal entries, products, customers, users, configurations, anything.
How it works — 3 protection layers
Automatic capture
Every CREATE, WRITE, DELETE on chosen models is sealed instantly with SHA-256 hash + client IP + user + timestamp.
Weekly verification
Scheduled task recomputes all log hashes and alerts Compliance Officers if any tampering evidence is detected.
Dashboard + reports
Live KPIs, user ranking, most-touched models, global integrity status. PDF/Excel reports ready to hand to auditors or regulators.
The log is tamper-proof — forensic-grade
-
🔒 Triple-layer immutability — No user, not even administrators, can modify or delete entries.
unlinkand arbitrarywriteraiseUserError. - 🧬 SHA-256 with per-database secret salt — Cryptographic salt unique per DB. Any modification breaks the hash and is detected.
-
✅ Automated weekly integrity check — Cron recomputes hashes and flags any mismatch as
tampered. Compliance Officer gets immediate alert. - 🌐 Client IP tracking — Captures real IP even behind proxy/load balancer (X-Forwarded-For, X-Real-IP support).
- 👥 Role-based access — Audit User (read-only) vs Compliance Officer (full config + reports). Separation of duties from day one.
🛡️ Multi-Standard Compliance Audit Trail
SHA-256 chained hashing + 2-year retention + weekly automated verification + IP tracking. Ready for ISO 27001, SOX, GDPR, PCI DSS and regional cybersecurity laws.
Meets the standards your auditors check
| Standard | Requirement | Meets |
|---|---|---|
| ISO 27001 A.12.4 | Logging and monitoring of security events | ✓ |
| SOX Section 404 | Internal controls over financial reporting | ✓ |
| GDPR Art. 30 | Records of processing activities | ✓ |
| PCI DSS Req. 10 | Tracking and monitoring of access to cardholder data | ✓ |
| NIST 800-53 AU-3 | Content of audit records | ✓ |
| HIPAA §164.312(b) | Audit controls for protected health information | ✓ |
Compatibility
Backports to Odoo 17.0 and 18.0 available on request — contact contacto@neurodev.cl.
Tech stack
- Python 3 + Odoo ORM — capture, hashing, integrity
- OWL 2 + Chart.js — reactive dashboard
- QWeb + xlsxwriter — reports
- ORM-level hook — does not require modifying existing models
License
OPL-1 (Odoo Proprietary License v1) — perpetual, single-database license.
Source code published on github.com/neurodev-apps for transparency
and community auditability.
Questions before installing?
Direct support from the developer. Remote installation and compliance advisory available.
🌐 neurodev.cl · ✉️ contacto@neurodev.cl · 📱 WhatsApp +56 9 2837 4712
Built by NeuroDev — Chile · neurodev.cl
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module