Merry Christmas & Happy 2027! Less downtime. More good times. Celebrating 13 years of sorlavit.com
Skip to content
Sorlavit KimIT Support, Network & Infrastructure Services Let’s talk
SORLAVIT / INTERACTIVE DEMO LAB

Explore the systems
before planning your project

Explore segmented access, system monitoring and recovery readiness. Change the scenarios to see how I approach the care of your IT systems.

Synthetic data only
This simulation illustrates a working approach. It is not a client case study or live dashboard and does not connect to or modify real systems.
Your selections persist in this browser session. Each section is saved independently and can be reset separately.
01 / OFFICE NETWORK

Who should have access to what?

This model office separates staff, guests and administrators to help contain the impact of a compromised or faulty device.

Useful for: Offices that need to separate guest Wi-Fi from business data and management tools.

Internet
Firewall / Router
Check inter-VLAN policies
VLAN 10 · Staff
Staff devices
VLAN 20 · Guest
Guest Wi-Fi
VLAN 30 · Admin
Management devices
Server segment
File / Management
GUESTFirewall · DEFAULT-DENY-00✕ DENY · Blocked at firewallFILES · Unreachable

Test the access policy

Default example · Not started yet

Connection denied

Guest · VLAN 20 → Firewall policy → File Server · SMB

Denied by least-privilege policy: this VLAN is not permitted to access the destination

For a real deployment, check firewall rules, network routes and user permissions, then test from the endpoint.
View simulated evidence and criteria
Source
Guest · VLAN 20
Destination
File Server · SMB
Matched rule
DEFAULT-DENY-00
Policy decision
DENY
View the model office policy
  • Staff: HTTPS to the internet and SMB to the file server
  • Guests: HTTPS to the internet only
  • Administrators: access to all example destinations from designated management devices
  • Other connections are denied by default. This model checks only the selected paths and services, not a complete firewall ruleset.
Discuss your office network →
02 / MONITORING & INCIDENTS

Spot abnormal behavior
and know what to do next

Choose an incident, then acknowledge, remediate and recheck it. Restarting alone may not address the cause. No real alerts are sent.

Useful for: Businesses that need to know when a system is unhealthy, who owns the response, and whether a fix has been verified.

Default example · Not started yet

Changing selections restarts this scenario. Other sections retain their results.
CPU24%
Disk usage48%
Latency18 ms
LAB-SRV-01Responding

Normal · No alert

The sample values do not meet the alert conditions.

Response approach: Track trends and review backup results on schedule.

  1. Detect and assess the incidentCurrent step

    The sample values do not meet the alert conditions.

  2. Acknowledge and identify the impactPending

    Waiting for the preceding step

  3. Apply the selected remediationPending

    Waiting for the preceding step

  4. Recheck and summarize the outcomePending

    Waiting for the preceding step

View simulated evidence and criteria
Simulated CPU
24%
Simulated disk usage
48%
Simulated latency
18 ms
Before remediation
Normal operation
Workflow stage
Detect and assess the incident
After remediation
Not yet verified
Criteria
Disk > 85% for 10 minutes; host unresponsive for 3 checks at 60-second intervals
Example alert thresholds
  • Warning: disk usage above 85% for 10 minutes
  • Critical: server unresponsive for 3 consecutive checks, 60 seconds apart
  • All values come from predefined scenarios, not live measurements. Real thresholds and notification channels depend on the system and agreed service hours.
Discuss monitoring →
03 / BACKUP & RECOVERY

You have a backup.
Can you recover within your targets?

Select an incident, a backup copy and its recovery point age to assess simulated availability and the RPO target. Then check the copy, restore, test and accept the result.

Useful for: Businesses with important data that need usable recovery copies and clearly explained test results.

Default example · Not started yet

Changing selections restarts this scenario. Other sections retain their results.

Simulation in progress · Plan the recovery point

The recovery point is 4 hours old, within the 4-hour target.

Real recovery steps: restore into an isolated environment, verify completeness and permissions, test files and applications, obtain user acceptance, and record the elapsed time.

This model assumes an intact backup has been verified and is usable. Recovery point age represents potential data loss, not recovery time (RTO). No actual restore is performed and recovery is not guaranteed.
  1. Plan the recovery pointCurrent step

    Recovery point age: 4 hours; RPO target: 4 hours

  2. Check backup availabilityPending

    Waiting for the preceding step

  3. Restore into an isolated environmentPending

    Waiting for the preceding step

  4. Verify files and test the applicationPending

    Waiting for the preceding step

  5. Accept and record the outcomePending

    Waiting for the preceding step

View simulated evidence and criteria
Recovery point age
4 hours
RPO target
4 hours
RPO result
Passed in the simulation
Acceptance status
Not yet accepted
Actual RTO
Not measured; an actual restore test is required
How do RPO and RTO differ?

RPO: The acceptable data loss window, for example 4 hours. A backup from 24 hours ago would not meet that target.

RTO: The target time to restore service. Actual recovery duration must be measured in a real restore test. This simulation does not calculate RTO.

Isolated copies need appropriate permissions, retention and regular restore tests. Immutable or offline storage alone does not guarantee recovery.

Discuss backup and recovery →
04 / CLEAR HANDOVER

A clear handover for ongoing care

Example documents that can be included in a real project. Details depend on the systems and scope agreed before work begins.

  1. System overview: Device inventory, project scope and system diagrams
  2. Change record: Changes, approvers and rollback plan
  3. Acceptance checklist: Test steps, results and outstanding follow-up actions
  4. Operation notes: Operating guidance, review schedules and incident contacts

Select “View report / Print PDF” to see your selections, simulated results, evidence and current workflow stage. Print or save a PDF through your browser, or download Markdown for later review.

References and further reading

The scenarios, content and interface were developed for Sorlavit using concepts from the following documentation.

Fortinet · Policy lookup ↗Zabbix · Problem acknowledgment ↗Veeam · Recovery verification ↗Product names belong to their respective owners. This page does not connect to those products or imply partnership or endorsement.
LET’S TALK ABOUT YOUR SYSTEMS

Want to apply this to your systems?

Tell me about the problem, number of users and desired improvements so we can discuss an appropriate scope.

Discuss your IT project Back to home