What is a one sentence summary of your feature request?
Enable a secure, least-privilege backup transfer and storage model that removes the need for reverse access from protected domains to backup locations
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
In many enterprise environments, identity infrastructure is segmented and governed by strict security policies, often limiting or prohibiting cross-domain access and trust relationships.
Current backup mechanisms for directory recovery can require service accounts or agents to write data back to a centralized file share. This introduces several challenges:
• Requires bidirectional access between environments, which may violate security policies
• Increases risk exposure for highly sensitive directory backup data
• Complicates deployment in no-trust or restricted network architectures
Organizations handling directory backups are particularly sensitive to how this data is stored and accessed, as it may allow reconstruction of identity infrastructure if compromised.
A more secure and flexible approach could include:
• Alternative transfer models (e.g., pull-based, brokered, or token-based access)
• A hardened backup vault with:
○ encryption at rest and in transit
○ strict access controls
○ auditability
○ isolation from production environments
This would enable deployment in highly regulated environments while aligning with zero-trust principles.
How do you currently solve the challenges you have by not having this feature?
Organizations often:
• Relax security controls to allow required access
• Introduce additional infrastructure to isolate environments
• Accept operational complexity to meet security requirements