Defense in depth
Several layers, one objective
Protection does not rely on a single control. We combine access controls, per-organization segregation, traceability, and managed infrastructure to reduce the attack surface and contain incidents.
Security and trust
Enterprise-grade security, documented for your vendor evaluation.
Clear controls and traceable results, ready for review by your IT and procurement teams.
Checklist for IT
What your IT team can evaluate
- Roles and two-factor authentication
- Isolation by organization or by dedicated instance
- Auditing and backups
- Files with controlled access
Pillars
Airtight privacy · Contractual backing · Control and compliance
Least privilege
Each person sees only what applies to them
Roles, permissions, and per-resource policies define what each user can view or modify. In multi-organization environments, data and branding stay scoped to the active tenant.
Verifiable evidence
Traceability ready for audit
Policy acceptance, logged activity, certificates with controlled public verification, and scheduled backups make it possible to demonstrate compliance with facts, not generic statements.
Controlled evolution
Changes with a record and continuity
Product updates are deployed in a planned way. Relevant changes are documented in the system’s public history when applicable, and production operation prioritizes availability and recovery.
Application layer
Controls built into the product
These mechanisms are part of Pullmío’s operational core and apply to every deployment, regardless of the contracted modality.
Authentication and sessions
Panel access via application credentials, with automatic logout on inactivity and session flows aligned with web best practices.
Two-factor authentication
Optional additional verification from the user profile. Recommended for administrators, coordinators, and accounts with broad access to sensitive data.
Roles and permissions
Authorization model based on role and granular permission, with per-resource policies that validate every action before exposing data or allowing changes.
Per-organization isolation
In multi-organization mode, each tenant operates with separate data, branding, and audiences within the same logical environment, with security context scoped to the active tenant.
Controlled files and downloads
Evidence, certificates, and sensitive attachments are served through protected routes or signed URLs with expiration, rather than permanent open links.
Audit and policies
Logging of relevant activity, mandatory acknowledgment of internal policies when configured, and usage limits on public surfaces to mitigate automated abuse.
Production infrastructure
Managed hosting platform
In production, Pullmío runs on a managed hosting platform specialized in mission-critical web applications. We do not publish the provider’s commercial name on this page; if your evaluation process requires it, we share it under a confidentiality agreement along with the contractual documentation.
Managed production hosting
The production instance runs on a managed hosting platform built for enterprise web applications, with teams that maintain the runtime, load balancing, and base components of the environment.
Encrypted communications
Traffic to the production application is served over HTTPS. Certificates and TLS termination are part of the environment’s standard operation, not an optional add-on.
Separate environments
Development, testing, and production remain isolated. Production deployments follow a controlled flow to reduce accidental changes to real data.
Private object storage
User files, media, and backups are hosted in S3-compatible object storage, with access restricted from the application and no direct public exposure of the bucket.
Managed database
Transactional data resides in a managed database service, with backups managed by the platform and restoration in line with the service agreements.
Perimeter protection
The network layer includes abuse mitigation and filtering at the hosting provider’s perimeter, complementing the application’s own rate limits and controls.
Responsibility is split explicitly: the hosting provider maintains the availability and security of the managed layer (network, runtime, managed database, and storage); the product team applies best practices in code, permissions, and application operation.
Continuity
Backup, recovery, and operation
Service continuity combines automatic backups, internal restoration procedures, and the production environment’s SLA.
- Scheduled backups
- Automatic copies of the database and configuration, with retention and periodic cleanup defined in the system’s operation.
- Documented recovery
- Restoration procedures are part of internal operations; in dedicated instances, scope is agreed contractually with your organization.
- Operational monitoring
- Oversight of the production environment to detect downtime or degradation and act before it impacts end users.
- Platform updates
- Patches and improvements from the hosting provider are applied at the managed layer, while application updates follow their own review and deployment cycle.
Need the detail for a security evaluation?
We can share the responsibility matrix, backup scope, data isolation modality, and hardening recommendations by role in a technical session with your team.