Solenor
Solenor
Solenor
Solenor

Security & sovereignty

Control over your deal environment

Confidential transaction work requires a deployment and access model that your IT, security, and engagement teams can review. Confirm the controls applicable to your environment before sharing deal data.

Deployment boundaries

Discuss private hosting and company-controlled deployment options with the team. Establish where documents, transcripts, model requests, backups, and outputs are processed for your selected configuration.

Hosting location alone does not establish compliance. Review contractual terms, subprocessors, support access, and operational responsibilities alongside the infrastructure design.

Access and engagement isolation

Define authorized users, administrator responsibilities, and boundaries between clients and engagements. Agree how access is provisioned, reviewed, and revoked, including access through connected datarooms and collaboration tools.

Models, sources, and verification

Model choice and external connectors affect the processing boundary. Confirm which models are enabled and the relevant provider terms, including retention and training policies, for your deployment.

Review source-linked outputs against the original evidence. Generated findings support the engagement team; they do not replace review or professional sign-off.

Security review before a pilot

Request a deployment walkthrough covering encryption, access logs, backup and deletion procedures, incident handling, and connector permissions. Certifications, service levels, and specific controls should be supported by documentation rather than assumed from the showcase.

Security review

Review your deployment requirements with the team

Discuss infrastructure boundaries, model governance, and engagement access before starting a pilot.