⚡Quick answer -

MyOperator uses AWS-based “defence-in-depth”: private VPCs, encrypted storage, TLS-only traffic, RBAC, 24 × 7 monitoring, and an audited incident-response plan. You control user roles, IP allowlisting, MFA, and data export.

When should I use this guide?

Read this if you :

• need to reassure stakeholders about data security, or
• Want a checklist of customer-side actions—IP allowlisting, MFA, and log reviews—to meet your internal policies.

1 — Cloud security at a glance

• Hosting: AWS, isolated Virtual Private Cloud (VPC)

• Encryption:

 – At rest → AES-256 on all storage

 – In transit → TLS 1.2+ for every endpoint

• Access control: Role-based (RBAC), MFA, optional IP allowlisting

• Monitoring: IDS, malware scans, central logs, 24 × 7 SOC

• Certifications: AWS ISO 27001, GDPR-aligned processes

• Change management: Peer code review, CI security scans, monthly pen-tests

Watch the video walkthrough

2 — Protections by layer

3 — Incident-response workflow

Alt-text: “Monitor → Detect → Contain → Notify customer if SLA impacted → Post-mortem.”

4 — Customer controls (what you can do)

1. Enable MFA – Settings → Security → Multi-factor.
2. Use least-privilege roles – Settings → Users: give each agent exactly what they need.
3. Turn on IP allowlisting (see next section).
4. Review access logs weekly – Reports → Audit.
5. Rotate API keys every 90 days under Settings → API Keys.

5 — How-to: enable IP allowlisting in

Repeat for all office / VPN IPs.

6 — Verify & monitor security

✓ Dashboard → Security shows “MFA enforced” and green IP-allowlist badge.

✓ Attempt login from an unallowed IP → receives 403 Forbidden.

✓ Audit Log records the last 30 days of role changes and login events.

7 — Limits and shared responsibility

No cloud is 100 % breach-proof; your configuration and user hygiene matter.

Keywords - MyOperator security, cloud encryption, AWS VPC, IP allowlist, MFA, incident response