Information Security Policy
Ferrazio · CNPJ (Brazilian company ID) 64.008.257/0001-72
Version 1.0 · effective since November 3, 2026 · reviewed yearly or after any relevant change
Security contact: privacidade@ferrazio.com
Download this policy as a PDF (Portuguese)
1. Purpose and scope
This policy sets out the rules Ferrazio follows to protect the confidentiality, integrity and availability of information handled on the Ferrazio Hub platform (ERP, marketplace integrations such as TikTok Shop, tax document issuing and customer support), on the ferrazio.com website and in the company's internal environments.
It applies to all partners, employees, service providers and suppliers who access systems or data of Ferrazio or its customers.
2. Principles
- Least privilege: each person and each system receives only the access strictly necessary for its function.
- Deny by default: any access not explicitly authorized is blocked.
- Defense in depth: no single protection is considered sufficient.
- Customer segregation: each merchant's (tenant's) data is logically isolated from the others.
- Traceability: relevant actions are logged and auditable.
3. Roles and responsibilities
| Role | Responsibility |
|---|---|
| Management | Approve this policy, provide resources and formally accept residual risks |
| Security Officer and Data Protection Officer (DPO) | Maintain the policy, coordinate vulnerability management and incident response, and serve data subjects and authorities |
| Technical team | Apply the controls described here and report flaws and incidents immediately |
| All internal users | Comply with the policy and the Confidentiality Agreement |
4. Information classification
| Class | Examples | Handling |
|---|---|---|
| Restricted | Passwords, API and signing keys, marketplace App Secrets, OAuth tokens, A1 digital certificates, encryption keys | Only in an encrypted secrets vault; never in code, email, chat or screenshots; named, minimal access |
| Confidential | Buyers' personal data (name, address, phone, CPF/CNPJ), orders, support messages, tax invoices, merchants' financial data | Encrypted in transit and at rest; access only as needed for the service; isolated per customer |
| Internal | Technical documentation, source code, operational metrics | Access restricted to the team; private repositories with MFA |
| Public | Corporate website, published policies | No restriction |
When in doubt, information is handled at the highest applicable class.
5. Encryption
- In transit: all external traffic uses HTTPS/TLS 1.2 or higher; internal communication between services (e.g. messaging) uses TLS with an internal certificate authority. Unencrypted connections are refused.
- At rest: production disks and databases are encrypted. Secrets, digital certificates and customer files receive an additional layer of encryption using key-encryption keys (KEK).
- Key management: keys are kept in a vault with restricted access (permission 0700), separate from backups, and are rotated immediately if exposure is suspected.
- User passwords: stored only with a strong hash and salt; never in clear text.
6. Access control
6.1 Platform users (merchants)
- Authentication with an opaque, short-lived session that can be revoked at any time.
- Multi-factor authentication (TOTP with recovery codes) and mandatory re-authentication (step-up) for sensitive actions.
- Role-based access control (RBAC) in fail-closed mode: without explicit permission, access is denied.
- Multi-tenant isolation: every query is filtered by the customer identifier.
- Rate limiting, and error messages that do not reveal internal information.
6.2 Administrative and team access
- Individual, named accounts; shared accounts are prohibited.
- Mandatory MFA on all corporate and supplier systems (code repositories, cloud providers, CDN/DNS, email, marketplace panels).
- Server access only through a VPN (WireGuard) and SSH with a cryptographic key; password login and direct root access are disabled; automatic blocking of attempts (fail2ban).
- Access is granted on a need basis, reviewed quarterly and revoked immediately when someone leaves or changes role.
- Team access to customer data happens only for requested support or legal obligation, and is logged.
7. Network and infrastructure security
- Network segregation: the platform sits behind a CDN with a web application firewall (WAF), DDoS protection and rate limiting. The origin server accepts web connections only from CDN addresses; databases, queues and cache are not exposed to the internet and listen only on internal interfaces.
- Services run in containers without root privileges (rootless), with resource limits and separate internal networks.
- Development, staging and production environments are separate; real customer data is not used outside production.
- Operating systems and components receive security updates regularly.
- Files uploaded by users go through antivirus scanning (ClamAV) with quarantine before being stored.
8. Workstation baseline
Every computer used to access Ferrazio systems must have, without exception:
- Active, up-to-date antivirus/antimalware (e.g. Microsoft Defender);
- Operating system and browser with automatic updates;
- Encrypted disk (e.g. BitLocker / FileVault);
- Automatic screen lock within 5 minutes of inactivity, with a password;
- Strong login password (at least 12 characters) and a password manager;
- MFA on all work accounts;
- Operating system firewall enabled.
Storing Confidential or Restricted data on unmanaged personal devices, USB drives or unapproved cloud services is prohibited.
9. Secure development
- Code in private repositories, with review before merging.
- Automatic scanning for vulnerabilities in dependencies (e.g.
cargo audit) in the continuous integration pipeline. - No secrets in code; secrets accidentally exposed are rotated immediately and removed from history.
- Input validation, signature verification on webhooks and idempotent event processing.
10. Vulnerability management
- Continuous monitoring of dependency security advisories, with a weekly review.
- Fix deadlines counted from identification: critical: up to 7 days; high: up to 30 days; medium: up to 90 days; low: next maintenance cycle.
- Penetration test (pentest) at least once a year and after significant architecture changes; the latest was performed on August 28, 2026, with a tracked remediation plan.
- Channel for responsible vulnerability disclosure: privacidade@ferrazio.com, with an initial response within 72 hours.
11. Logging and monitoring
11.1 Risk engine (automatic detection and blocking)
The platform gateway has a risk engine, always on and with no off switch, that evaluates every authenticated request and assigns a risk score per user session and per API key. Among other things, it monitors:
- Attempts to access another customer's data or to scan identifiers: the request is denied with an opaque response (the system does not reveal whether the resource exists or belongs to another customer) and the attempt adds risk points;
- Change of device or network during the session (a sign of a stolen session or token);
- Repeated login attempts, MFA attempts or use of invalid API keys, with per-address limiting and temporary account lockout;
- Abnormal request volume, with rate limiting per address, user and key.
When thresholds are exceeded, the engine first slows down responses and then automatically blocks access. For users, blocking is progressive within 30 days (temporary, then longer and, for repeat offenses, permanent, reversed only after analysis). For integrations, the block falls on the suspicious API key, which must be revoked. Repeatedly issuing blocked keys leads to the responsible user being blocked. All events are recorded in an audit trail for investigation and may trigger the Incident Response Plan.
11.2 Logs
- Access, authentication and security event logs are centralized and kept for 30 days (or longer when required by law).
- Alerts for mass authentication failures, abnormal errors and unavailability.
- Logs do not store passwords, tokens or card data.
12. Backup and continuity
- Automated daily backup of all databases and files, with integrity verification (hash).
- A copy kept outside the main server.
- Weekly restore test.
- Backup retention: 7 days on the server and 14 days on the off-site copy; after that they are overwritten.
13. Suppliers
Infrastructure providers (hosting, object storage, CDN) are selected considering their certifications and security practices, and data is hosted in Brazil and the United States. Suppliers with access to personal data take on contractual confidentiality and data protection obligations.
14. Incidents
Security incidents are handled under Ferrazio's Incident Response Plan, which includes notifying customers, partner marketplaces (such as TikTok Shop) and Brazil's data protection authority (ANPD) within the applicable deadlines.
15. Awareness
All employees receive security and privacy guidance when they join and annual refresher training, and sign a Confidentiality Agreement.
16. Non-compliance
Failure to comply with this policy may result in revocation of access and disciplinary and contractual measures, without prejudice to legal liability.