Security at Plus Two Sigma

Your plant.
Your boundaries.

A platform for engineering decisions, with clear boundaries around your data, your people and your control systems.

Explore our approach
The plant boundary
Level 3 and abovePlus Two SigmaInvestigate · Analyze · Review
Approved data sources
Read-only by default
Your plant dataHistorian · LIMS · MES · Documents
Reach set by your organization
Control systemsDCS · PLC · SIS
Logical boundary. Network placement and permitted connections are agreed with your IT and OT teams.
01 / Plant boundary

Engineering insight.
Control stays with you.

Plus Two Sigma operates at Purdue Level 3 and above. It reads the data made available to it to help your engineers investigate issues, analyze performance and prepare work.

Your organization decides what it can reach. Approving a process recommendation records a decision; it does not change a setpoint or send a command to a DCS, PLC or safety instrumented system.

Your existing operating procedures and control systems remain responsible for plant operation.
02 / Deployment

Start with your network requirements.

Application hosting and AI processing are separate choices. Agree both before connecting plant data.

01

On your network

Host the application and its stores in your environment. Local model endpoints are supported for inference.

Review every enabled service before treating a deployment as fully offline.

02

Private cloud

Plan a deployment in infrastructure your organization manages, with network access and storage policies set by your IT team.

Hosting, identity and operational requirements are scoped for each deployment.

03

Hybrid

Keep application data in your environment while using an external model service for selected workflows.

External processing can include prompts, retrieved context and tool results.

03 / Data handling

Know where
your data goes.

A local installation alone does not mean every feature runs locally.

AI processing
Cloud model configurations send request content to the configured provider. Retrieval can also use an external embedding service. Review both paths when deciding what may leave your network.
Storage & retention
Documents, conversations, analysis results and audit records can be stored by the application. Define retention, deletion and backup handling for the deployment before use.
Encryption & network access
Configure HTTPS, storage encryption, network segmentation and restricted service access with your IT team. These protections depend on the hosting environment.
Model-provider terms
Review the selected provider’s data-use, training and retention terms as part of deployment. They are separate from where the application is hosted.
04 / Access & audit

People make the decisions.
The platform keeps the record.

Account-based access

Administrators manage accounts and permissions for agent use, connection management and signing decisions.

A person signs the decision

Proposed actions go through an approval or rejection step. The record includes the signed-in account and the decision.

A record you can review

Action decisions are written to an append-only, hash-chained audit log. Access to the log and its storage is managed in your deployment.

Infrastructure access, backup protection and log retention are part of the deployment review. Hash chaining supports integrity checks; it is not immutable storage.

05 / Standards & assurance

Clear references.
Clear status.

These frameworks provide context for evaluating AI governance and security controls. The capabilities described here are not a statement of conformity or independent assurance.

AI management

ISO/IEC 42001

An organizational management-system standard for responsible AI development and use, including governance, risk management and continual improvement.

Relevant product practicesHuman review of proposed actions and records of signed decisions.
Certification statusNot certified
About ISO/IEC 42001 (opens in a new tab)
Security assurance

SOC 2

An independent CPA examination of a service organization’s controls against applicable AICPA Trust Services Criteria. The result is an assurance report.

Relevant product practicesAccount permissions, controlled approvals and action audit records.
Report statusNo SOC 2 report
About SOC 2 (opens in a new tab)

These references do not imply endorsement, certification, a completed audit or full alignment with either framework.

Before connecting your plant

Bring IT into
the conversation.

Use your security review to agree the data sources, hosting environment, external processing and account permissions for your deployment.

  • Network boundaries and permitted connections
  • Model and embedding providers, and their data terms
  • Identity, encryption, retention and backup requirements
  • Support access and incident-response contacts
Discuss your requirements