Security without opening ports
Updated:
CoreDLS connects to the ERP with an agent that only makes outbound connections: it opens no ports on the customer network and does not write to the ERP tables. Access is per device bound to the person, each company data is separated, and backups are encrypted.
Technical answers for the IT team. Everything below describes how CoreDLS works; no certifications are claimed.
How the outbound-only agent works
- It is a lightweight service that runs as a Windows service on the customer network, next to the ERP server.
- It goes out to CoreDLS to fetch work every so often: it talks outward and nobody talks inward. Nothing is left listening on the customer firewall side.
- It reads from the ERP what it needs. When something new has to be recorded, it leaves it in CoreDLS own tables and the customer system processes them when it wants.
- On a failure it restarts on its own and retries with increasing waits; it leaves no half-executed commands.
- If the customer stops using CoreDLS, the ERP database stays as it was.
Encryption
- The app, the web and the agent talk to the platform over HTTPS.
- Backups are encrypted.
Per-device access
- The phone is bound to the person: an administrator enables the device once and then access is by fingerprint, face, PIN or pattern, with no username or password on the phone.
- Failed PIN or pattern attempts lock access for a while; the times are configurable per company.
- The web is entered by scanning a QR code from the app, which authorizes the session. The code expires within seconds and the web session lasts a few hours, extended with use.
- If someone loses the phone or leaves the company, the device is revoked from the administration and the session is closed.
- Each person sees only the modules enabled for them, and the console used to administer companies asks for a second factor in addition to the password.
- Each company data is separated: every company works in its own space.
Backups
- Continuous, encrypted backups, with alerts if something fails, so it is possible to go back to an earlier point.
- What is deleted in the system goes through a recycle bin and parameters keep their previous value.
Frequently asked questions
- Do I need to open ports on the firewall?
- No. The agent only makes outbound connections; nothing is left listening on the inside.
- Does the agent write to the ERP tables?
- No. It reads what it needs and leaves anything new in CoreDLS own tables, which the customer system processes when it wants.
- What happens if the internet drops or the agent fails?
- The agent restarts on its own and retries with increasing waits. On the phone, the app works with local data and queues what is entered until the connection returns.
- How is the web accessed?
- By scanning a QR code from the app. There is no password form for the web session.
- What if an employee loses their phone?
- The device is revoked from the administration and the session is closed. To get back in they need an administrator to enable the device again.
- Are there backups?
- Yes: continuous, encrypted backups, with alerts if something fails, so it is possible to go back to an earlier point.
You can request a half-hour demo: the app is shown with test data and technical questions are answered on the same call.