MFA Everywhere
Multi-factor authentication is enforced on all systems that support it.
How CyberConnect protects systems, handles data, and responds when incidents happen.
Multi-factor authentication is enforced on all systems that support it.
Critical data follows 3-2-1 backup strategy with verified recovery paths.
Unneeded endpoint services and exposed ports are closed by default.
Patch cycles run weekly with priority handling for high-severity issues.
Triage → contain/minimize risk → restore from backups → validate recovery.
Client data access is handled directly by Dorian Balogh (bonded, Level 2 security guard).
Data is kept private and never copied to other devices without explicit permission.
If copying is approved, retained data is held for a maximum of 30 days.
For regulated/medical-sensitive contexts, retained data is limited to 14 days.
Retention windows can be shortened further by written client request.
Emergency response target for active incidents.
General request and non-emergency response target.
Wazuh, FleetDM, and MeshCentral for monitoring, deployment, and remote management.
Native macOS backup tooling on Apple systems, Restic for other systems and repositories, plus Gitea for private software development history.
Prometheus + Grafana + Uptime Kuma (self-hosted) plus Ubiquiti hardware telemetry for network visibility.
Self-hosted Bitwarden for password and 2FA storage, plus retention policy for investigations.
Snipe-IT for asset tracking and deployment lifecycle visibility.
Self-hosted Open-WebUI and LM Studio with custom workspaces so data never leaves site.
Supports GDPR and HIPAA/HIPPA-conscious workflows when required by clients.
Aligns to PIPEDA (Canada) and PCI DSS baselines for payment-adjacent environments.
Uses CIS Controls as a practical hardening baseline for SMB environments.
Policies and technical controls can be mapped per client scope during onboarding.
Weekly restore spot-checks and monthly full restore drills for critical systems.
Continuity objectives defined by system priority (critical, important, non-critical).
Backup scope, recovery sequence, and single points of failure reviewed quarterly.
Tabletop incident simulation with clear communication and ownership paths.
For urgent containment support, use the priority incident contact section.
Include what was observed, when it started, and what systems are impacted.
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