Best-Effort Scrambling
Network and firewall faults get handled reactively on a best-effort basis only after multiple users lose connectivity.
CLOSED BY NETWORK ACCOUNTABILITY
✓
MANAGED NETWORK, FIREWALL & VPN SUPPORT
SERVICE FAMILY: EDGE
When the connection or firewall fails, who’s responsible for the fix?
THE WRITTEN PROMISE
The network and firewall you depend on, monitored and owned explicitly, not squeezed into user support.
100% Written Scope Boundary
3 Tiers START · CORE · STRATEGIC
Named Senior Ownership
Designated Layer Mandate
Network Accountability
Contract Family
EDGE
Delivery Model
Outcome-Based · Fixed Tier
Boundary Status
Inclusions & Exclusions Written
Escalation Point
Senior Cape Town Engineers
OPERATIONAL DIAGNOSTIC
Signs nobody owns this yet
Network and firewall faults have probably been handled reactively, on a best-effort basis. Network Accountability makes their availability a defined responsibility.
Recurring VPN & Wi-Fi Drops
The same connectivity, VLAN, or VPN problem keeps coming back every week without permanent isolation.
CLOSED BY NETWORK ACCOUNTABILITY
✓
Three-Supplier Finger-Pointing
When the internet drops, three suppliers each say the fault sits on someone else’s equipment.
CLOSED BY NETWORK ACCOUNTABILITY
✓
WRITTEN SCOPE ARCHITECTURE
What we own — and what stays separate.
Ambiguity is where IT partnerships break down. We publish both what is included in Network Accountability and what is scoped separately so your team never discovers a gap mid-incident.
[!] WHAT STAYS SEPARATE, AND WHY
Scoped separately: New rules and redesign · policy, segmentation, VLAN and QoS changes · Wi-Fi surveys and optimisation · major firmware upgrades · new deployments · ISP and cloud networking.
These change the network design, so they’re scoped and quoted as projects with their own sign-off.
CONTRACTED INCLUSIONS (5 CORE MANDATES)
FAMILY: EDGE
- Availability monitoring and alerting for network switches, routers, Wi-Fi controllers, and security appliances
- Fault isolation, device and service restarts, interface resets, and firmware crash recovery
- VPN tunnel resets and rollback of existing firewall rules (plus certificate rebind and renewal)
- Proactive availability management and preventative maintenance CORE
- Unlimited in-scope incidents, limited after-hours cover for critical P1 outages, and hardware escalation to the vendor CORE
OPERATIONAL REALITY CHECK
Coverage and ownership are not the same thing.
GOOD TO KNOW // OPERATIONAL BOUNDARY RULE
Proactive support keeps your existing design running. Redesign, VLAN restructuring, and performance tuning are projects. We support Reyee, Ubiquiti, Sophos, and network devices explicitly approved by Crimson Line.
SERVICE TIER ARCHITECTURE
Network Accountability Tiers
Delivered across two separable packages — Network & Infrastructure, and Firewall & Security Appliance.
REACTIVE ENTRY
START
Monitoring plus reactive break/fix in business hours. No reporting.
Excludes trend visibility, root-cause incident summaries, preventative maintenance, and configuration changes.
SWITCHING, ROUTING & WI-FI
RECOMMENDED
CORE: Network
Proactive availability management and unlimited in-scope incidents.
Includes preventative maintenance, reachability restoration, port/VLAN fault resolution on existing config, and incident summary per issue.
PERIMETER, VPN & WAF
RECOMMENDED
CORE: Firewall & WAF
Proactive firewall and WAF availability, VPN recovery, unlimited in-scope incidents, and limited after-hours cover for critical outages.
Covers HA/failover restoration, VPN tunnel resets, certificate renewals, existing-rule rollback, and direct vendor escalation.
Our services are deliberately modular. Network, backup, security depth, server and cloud are separate commercial decisions — never bundled implicitly into per-user pricing.
CONNECTED ACCOUNTABILITY LAYERS
What connects with Network Accountability
Every layer is modular by design and integrates cleanly with adjacent operational responsibilities.
QUESTIONS & CLARIFICATIONS
Network Accountability FAQs
What happens when our upstream fibre or ISP line goes down?
Instead of leaving you caught between an ISP and an IT support desk, we isolate whether the fault is on your firewall/switching gear or the upstream circuit and manage the technical escalation with the ISP.
Why are new firewall rules or VLAN changes treated as projects?
Maintaining availability within an agreed design is routine operations. Altering firewall policies or network segmentation changes your security and routing posture, so it is scoped, reviewed, and signed off explicitly.
NEXT STEP