NDC360 stores data in enterprise-grade databases such as PostgreSQL and Neo4j, with controlled access, audit logging, and encryption-ready infrastructure. It secures access through centralized authentication with Keycloak and LDAP/AD, applies role-based access control, and maintains detailed audit and change logs to ensure strong data protection and full traceability of all operations.
Changes are tracked and audited through detailed logging and version control mechanisms that record who made a change, what was modified, and when it occurred. This ensures full transparency and traceability across the platform. Audit logs provide a historical view of all actions, enabling teams to review changes, investigate issues, and maintain compliance with internal policies and external regulations.
NDC360 supports deployment in restricted and air-gapped environments, including on-premises infrastructures with limited or no external connectivity. Updates and integrations are handled through controlled, secure processes to ensure compliance with internal security policies and regulatory requirements.
Sensitive network data is protected through a combination of access control, encryption, and continuous monitoring. Role-based access ensures that only authorized users can view or modify critical data, while encryption safeguards data both in transit and at rest. In addition, audit logs and real-time monitoring help detect and respond to suspicious activity, supporting compliance and reducing the risk of data breaches.
User authentication in NDC360 is handled through your organization’s existing identity providers - such as Active Directory, Azure/Entra ID or AWS - so users log in with their familiar corporate credentials. Once authenticated, the platform applies role‑based access control: administrators assign each user a role that defines their permissions and access scope, ensuring that the right people manage the right systems. These roles can be tailored to match your workflows, providing granular security and compliance without maintaining a separate user database.