Before
- Customers across different tools
- Assets and documents kept apart
- Time and materials elsewhere
- Reports outside the context
ED Nexus
Security and reliability
Choosing IT software also means reviewing your company's requirements. Use the demo request to tell us which topics you would like to discuss. Do not include credentials or confidential information.
Security
Security with documented limits.
The Security page presents documented controls, usage conditions and their limits.
- Documented controls
- Visible limits
- Verification still required
- No implied certification
Documented architecture with a separate instance and database per subscriber
Describes the documented architecture; the effective configuration may vary.
Isolation controls
Application-level isolation controls; not an independent certification.
Vault credentials are encrypted before storage
Limited to credentials stored in the vault and their associated key management.
Security controls for the documented scope
Application-level controls for the documented scope; not an independent certification.
Log of supported actions
Event coverage, retention, roles and integrity properties must be defined before broader wording is used.
Discuss your security requirements
- Team access and responsibilities
- Handling credentials
- Information retention
- Availability and recovery requirements
Before and after
From distributed work to a shared context.
With ED Nexus
- Customer as operating context
- Information linked to the customer
- Time and materials on the intervention
- Reports linked to the work
Let's talk about your IT work.
Customers, infrastructure, interventions: which activity would you like to start with?