Security · NISKA

Our commitment

Hospitality systems handle sensitive operational and guest-related data. We design NISKA with defense-in-depth controls, least privilege, and auditability so properties can trust agentic automation without surrendering governance.

Platform controls

We use encryption in transit (TLS), hardened hosting environments, network segmentation where applicable, continuous monitoring, vulnerability management, and secure software development practices including code review and dependency hygiene.

Data protection

Customer data is logically separated by tenant. Backups and retention follow configured policies. Production access is restricted, logged, and reviewed. Secrets and credentials are stored using secure secret management—not in source control.

Identity and access

Customer admins control user roles and permissions inside NISKA. We support strong authentication patterns for product access and apply internal MFA and least-privilege access for NISKA staff who support the platform.

Incident response

We maintain incident response procedures for detection, containment, investigation, and customer notification consistent with contractual and legal obligations. If you believe you have found a vulnerability, contact security@niskagroup.com.

Subprocessors and vendors

We evaluate critical subprocessors for security and privacy posture and bind them contractually to protect customer data. A current subprocessor list can be provided to customers under NDA upon request.

Shared responsibility

Customers are responsible for configuring roles, agent permissions, integrations, and property policies appropriately; protecting their own endpoints and credentials; and promptly notifying NISKA of suspected account compromise.

Contact

Security questions, reports, and customer assurance requests: security@niskagroup.com. For privacy-related requests, use privacy@niskagroup.com.