Data is the new oil, but giving this oil uncontrolled to pipelines can result in disaster. The biggest fear of businesses is that sensitive data (salary information, cost analyses, customer data) falls into unauthorized hands during integration projects.
In traditional methods, when you give a developer database access, you usually open "all doors." iDataEngine V4.1 supports "Zero Trust" architecture thanks to the security layers of the REP and API modules.
Granular Authorization (Fine-Grained Authorization)
In iDataEngine, authorization is not at the "table" level, but at the "data content" level.
- Field-Level Security: A user can pull the "Employee List" report, but if they don't have permission, they cannot see the "Salary" column. The REP module automatically masks or returns that column empty when pulling data according to the user's authorization.
- Row-Level Security: The Istanbul Regional Manager only sees Istanbul data. Ankara data doesn't exist for them.
API Security: The Guard at the Gate
Our API module works like a firewall for your services that open to the outside world.
- IP Restriction: Your critical financial APIs can only be accessed from the Finance department's static IP.
- Token Management: With temporary and time-limited access tokens, you can cut an integrator company's access to your system with a single click when the project ends.
- Rate Limiting: Prevents a malicious or incorrectly written external application from locking your system (DDoS) by sending 1000 requests per second.
Secure Delivery in MF Module
The biggest risk in mail and file transfers is the wrong file going to the wrong person.
- Dynamic Receiver Lists: The MF module can dynamically get the list of people to send the report to from the current ERP hierarchy, not from a static table. Thus, a report never goes to a manager who has left the job.
In Summary: With iDataEngine, you never lose control while liberating data. The key is always in your hand.