CoreNova Intelligence

CoreNova Intelligence Limited

Security & compliance boundaries

CoreNova provides a verifiable hardened starting point; buyers retain responsibility for risk assessment, workload configuration, and compliance decisions.

Last updated: July 10, 2026

Common baseline

  • SSH key-only access with root and password login disabled.
  • Host firewall, auditd, rsyslog, chrony, AIDE, and automatic security-update baselines.
  • Product-specific AWS Systems Manager, GPU, or application-runtime configuration where documented.

CIS and OpenSCAP boundary

Products use CIS-oriented baselines and OpenSCAP materials to support buyer validation. CoreNova products do not claim to be officially CIS-certified images.

Results depend on OS version, configuration, exceptions, patch timing, and buyer workloads. Organizations must perform final validation in their own AWS accounts.

Buyer responsibilities

  • IAM, EKS Access Entries, Kubernetes RBAC, security groups, VPC design, and inbound access.
  • Keys, credentials, models, data, backups, log retention, and patch policy.
  • Regulatory, privacy, licensing, and software-dependency review required for the workload.

Report a security issue

Report potential security issues to support@corenovacloud.com. Do not include private keys, credentials, customer data, or directly exploitable sensitive material in the first email.