← Back to Actonyx

LEGAL / Draft for review

Security Policy

A practical guide to the security questions and evidence to discuss before a product deployment.

Scope of this draft

This draft is a product-security evaluation guide. The topics below are questions to assess with your team, not assertions of implemented controls, certifications, authorization to operate, or suitability for classified information.

Deployment boundaries

Start with the environment, data classification, and operational boundaries of the proposed deployment. Confirm requirements for each environment separately.

  • Where will processing, storage, and administration occur?
  • Which network connections, external services, and operator responsibilities are required?
  • What isolation, connectivity, and update constraints apply to the proposed environment?

Identity and access

Request evidence for how users, administrators, and service identities are managed in the proposed configuration.

  • Which authentication and identity-provider integrations are available?
  • How are permissions, privileged access, and service credentials scoped and reviewed?
  • How are access removal and account lifecycle changes handled?

Data handling and protection

Map the lifecycle of images, video, annotations, predictions, and exported data. Establish responsibilities in the relevant agreement.

  • Where does data travel, and which parties can access it?
  • What encryption, key-management, retention, deletion, and backup arrangements apply?
  • What restrictions govern sensitive data, exports, and use of third-party services?

Models and artifacts

Evaluate the provenance and lifecycle of models, dependencies, and deployment artifacts alongside application security.

  • How are model sources, versions, dependencies, and approvals recorded?
  • What checks protect artifact integrity and the delivery pipeline?
  • How are model updates evaluated, released, and rolled back?

Logging and incident response

Discuss what can be observed and how responsibilities are shared when an issue occurs.

  • Which audit events are recorded, and how are logs protected and retained?
  • How are vulnerabilities, patches, and operational alerts managed?
  • Who handles incident escalation, customer notification, recovery, and follow-up?

Evidence for procurement

Request current evidence that applies to the specific product version, environment, and contractual scope under evaluation. No certification or independent assessment is asserted by this website.

  • Can the team provide an architecture review, data-flow description, and responsibility matrix?
  • Which assessments or test reports are available, and what are their scope and date?
  • Which requirements are supported today, require configuration, or need further evaluation?

Start a security conversation

Use Get in Touch for an initial security evaluation inquiry or website security concern. Share a non-sensitive summary and ask the team to establish an appropriate channel for further details.

Do not submit credentials, exploit payloads, classified information, or sensitive technical details through the public form. This guide does not establish a vulnerability disclosure program, response deadline, or safe-harbor commitment.

Questions about this draft? Use Get in Touch in the header to start a conversation.

Back to top ↑