Trust Center
How CyberConnect protects systems, handles data, and responds when incidents happen.
Security Practices
- Multi-factor authentication is enforced everywhere it is supported.
- 3-2-1 backup strategy is used for all business-critical data.
- Unneeded endpoint services and exposed ports are closed by default.
- Patch cycles run weekly with priority handling for high-severity issues.
- Incident workflow follows: triage, contain/minimize risk, restore from backups, validate recovery.
Data Handling
- Client data access is handled directly by Dorian Balogh (bonded, Level 2 security guard, trained).
- Data is kept private and is never copied to other devices without explicit client permission.
- If copying is approved, retained data is held for a maximum of 30 days.
- For regulated or medical-sensitive contexts (including HIPAA/HIPPA-like restrictions), retained data is limited to 14 days.
- Retention windows can be shortened further by written client request.
Response Commitments
24 hours
Emergency response target for active incidents.
48 hours
General request and non-emergency response target.
Tooling Stack
- Security and fleet control: Wazuh and FleetDM.
- Backups: native macOS backup tooling on Apple systems, Restic for other systems and repositories.
- Email security: Proxmox Mail Gateway.
- Monitoring: Prometheus + Grafana + Uptime Kuma (self-hosted) for service health, trends, and uptime visibility.
- Suggested additions: central secrets management (Bitwarden/Vaultwarden) and centralized log retention policy for investigation timelines.
Compliance & Governance Alignment
- Supports GDPR and HIPAA/HIPPA-conscious workflows where required by clients.
- Also aligns practices to PIPEDA (Canada), PCI DSS baselines for payment-adjacent environments, and CIS Controls for practical hardening.
- Policies and technical controls can be mapped per client scope during onboarding.
Business Continuity
- Documented backup validation schedule: weekly restore spot-checks and monthly full restore drills for critical systems.
- Minimum continuity objective: defined RPO/RTO targets by system priority (critical, important, non-critical).
- Quarterly continuity review for backup scope, recovery sequence, and single points of failure.
- Annual tabletop incident simulation with clear communication and ownership paths.
Contact for Security Concerns
If you suspect a compromise, account takeover, ransomware, or active abuse, use the incident route immediately.
- Use the priority incident contact section for urgent containment support.
- Include what was observed, when it started, impacted systems, and whether operations are currently disrupted.
- For sensitive disclosures, request an encrypted response path in your first message.
Need these standards implemented in your environment now?
Request a Security Implementation Plan