Skip to content
ANTE

Security

Security Overview

Last updated: 2026-10-20

← All security documents

Owner: Multibook Philippines Inc. · Version 1.2 · Last reviewed 2026-10-20 · Reviewed annually.

This overview summarises ANTE ERP (cloud)’s security posture across the areas customers and security teams most often review. The detailed policies behind it are linked from the security documentation index. Infrastructure / network diagrams and our providers’ compliance certifications are available to customers and prospects on request.

Hosting & architecture

ANTE is provided only as a cloud service; Enterprise customers can have a dedicated cloud instance. It runs on DigitalOcean (Singapore, SGP1) across a small fleet of servers in one private VPC, with Cloudflare at the edge and Vercel serving the static marketing/front-end CDN. Customer data and backups are stored in Singapore. In transit, data passes through Cloudflare’s global network, and some subprocessors process data outside the Philippines (see the Privacy Policy and Data Processing Addendum).

Network & access management

  • A host firewall (default-deny inbound) runs on every server. Public web traffic is locked to Cloudflare’s IP ranges — users reach the service only through the Cloudflare edge over HTTPS; origin IPs are hidden and direct-to-origin access is restricted.
  • Databases are bound to localhost and are not reachable from the network or internet — only the co-located application connects.
  • Administrative access is SSH key-only over a private (Tailscale) network; public SSH is closed. Inter-service traffic is restricted to specific private-VPC addresses.

Encryption

  • In transit: all access is HTTPS only, TLS 1.2 or later (older TLS versions are rejected).
  • At rest: database volumes are encrypted at rest (LUKS/AES-256) at the storage layer; passwords are stored only as one-way bcrypt hashes; API credentials and OAuth tokens are AES-256 field-encrypted; backups are encrypted at rest in object storage.

Authentication & access control

  • One account per user (enforced unique) and role-based access control (per-scope).
  • Sign-in uses passwords stored as one-way bcrypt hashes, account lockout (5 failed sign-ins within 15 minutes lock the account for 30 minutes), an emailed one-time code when signing in from a new device, and per-company idle timeouts. ANTE does not currently offer authenticator-app (TOTP) multi-factor authentication.
  • Sensitive administrative operations require an additional one-time-code confirmation, and all admin actions are recorded in an append-only audit log. Privileged server access is limited to a designated engineer. See the Privileged Access Policy.

Web application firewall & DDoS

  • Cloudflare WAF (Pro) protects public endpoints: managed rulesets, exposed-credential checks, rate-limiting on authentication endpoints, custom exploit-path blocking, and automatic L7 DDoS mitigation. Security events are logged at the edge, and the team is notified of detected attacks.

Vulnerability management

  • Three continuous, CI-blocking automated layers: dependency scanning (CVE alerts + automated fix PRs), static analysis (SAST), and container / IaC scanning. New vulnerabilities block the pull request; all container images run as a non-root user.
  • We welcome customers running their own standard vulnerability scan against the service and will remediate findings.

Backups & disaster recovery

  • Daily automated backups (03:00 Philippine time) of all production databases to off-server object storage (DigitalOcean Spaces, Singapore), kept for 30 days and encrypted at rest. Each run verifies the dump size and the upload, and failures alert the team. Worst-case data loss (RPO) is bounded to about 24 hours. We do not commit to a fixed recovery time (RTO). Restoring service is our top priority during an incident, and we keep customers informed through the status page and email.

Monitoring & alerting

  • Infrastructure monitoring agents report server and service health to a monitoring service. Alerts go to an internal Telegram group used by the engineering team. These alerts contain infrastructure metrics only, such as CPU, memory, disk and service status, and no customer records or personal data, so Telegram is not a subprocessor of customer data.
  • Internal security alerts and one-time codes for high-risk actions go to Multibook’s internal security channel on Slack, which is listed as a subprocessor.

Incident response & breach notification

Security incidents are reported to security@ante.work. If a personal data breach affects customer data, Multibook notifies the customer without undue delay and within 48 hours of becoming aware of it, so the customer can meet its own 72-hour notification period to the National Privacy Commission under NPC Circular 16-03 (see the Data Processing Addendum).

Logging & audit

  • A dedicated append-only audit database retained for up to 24 months from each event captures logins (with IP / user-agent) and all user and admin actions, providable on request. Web access logs are retained for about 12 months. See the Log Retention Policy.

Data handling, retention & deletion

  • Customer data belongs to the customer; Multibook does not access it without the customer’s request or prior approval (including support “log in as”, which needs a one-time code and is audit-logged), and all access is auditable (Customer Data Access Policy).
  • On termination, customer data is deleted within 30 days of request and ages out of backups within a further 30 days (Data Deletion & Offboarding Runbook).

Subprocessors & infrastructure certifications

  • Subprocessors: DigitalOcean (servers, databases, file and backup storage, Singapore), Cloudflare (DNS, CDN, WAF), Vercel (web front-end hosting), Amazon Web Services SES (system email, Singapore), Google (Sign-In, Calendar if enabled, Firebase push notifications), MiniMax (system AI for Pro AI features), Slack (Salesforce) (internal security alerts: one-time codes for high-risk actions are issued to Multibook’s internal security channel and include the requesting user’s name, email and company) and GitHub (source code and deployment automation; no customer data is stored there).
  • Optional, enabled by the customer: Slack, Facebook, the Multibook ERP connector, the customer’s own AI provider key and its own SMTP server.
  • The current list is on the Trust Center; changes are notified under the Data Processing Addendum.
  • Infrastructure providers are independently certified — DigitalOcean: SOC 2 Type II, ISO/IEC 27001; Cloudflare: ISO 27001, SOC 2 — see digitalocean.com/trust and cloudflare.com/trust-hub. Multibook operates ANTE with ISO 27001-aligned controls; ANTE itself is not ISO 27001 certified. A SOC 2 Type II audit of ANTE is in progress.

Availability & support

  • Availability target 99.5% (a target, not a guarantee), with independent 24/7 uptime monitoring. Support and recovery terms are in the SLA.

Reporting a vulnerability

Found a security issue? Please disclose it privately first — see the Security & Trust Center for our contact and response commitment.