bc-gov-sdn-zones

Classify workloads into SDN zones and define DataClass and egress policies.

7|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/rloisell/rl-agents-n-skills --skill bc-gov-sdn-zones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bc-gov-sdn-zones
Source: https://github.com/rloisell/rl-agents-n-skills/tree/main/bc-gov-sdn-zones
Command: npx skills add https://github.com/rloisell/rl-agents-n-skills --skill bc-gov-sdn-zones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BC Government workloads must be assigned to appropriate network security zones based on data sensitivity and policy constraints. This skill provides a proven framework to map ISCF classifications to SDN zones, guide zone adjacency, and plan compliant egress and partner connectivity.

Core Features & Use Cases

  • Map data classification to the correct SDN zone (Low/Medium/High) and assign the corresponding OpenShift DataClass.
  • Use zone adjacency rules to design safe, policy-driven workload connectivity and external access paths.
  • Plan Third Party Gateway (3PG) connectivity and non-internet egress paths in accordance with BC government standards.
  • Reference and apply the 2022 SDN Security Classification Model and historic IMIT zoning where necessary.

Quick Start

Apply the SDN zoning model to determine the correct zone and egress rules for a workload based on its data classification.

Frequently Asked Questions about bc-gov-sdn-zones

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map ISCF data classifications to SDN zones for OpenShift workloads?

To map ISCF data classifications to SDN zones, classify the workload's data sensitivity and assign it to the corresponding Low, Medium, or High SDN zone. This determines the correct OpenShift DataClass and egress policy guidance for compliant workload deployment.

What is the SDN zone model used for BC government network security?

The SDN zone model is a security architecture framework that categorizes BC government workloads into distinct zones based on data sensitivity. It enforces internet ingress and egress constraints, zone adjacency rules, and 3PG connectivity to maintain strict network security boundaries.

How do I plan Third Party Gateway (3PG) connectivity for BC government workloads?

Planning Third Party Gateway (3PG) connectivity involves defining non-internet egress paths according to BC government standards. The zoning process evaluates the workload's data classification to determine the safe, policy-driven external access paths and partner connectivity rules required.

Can I use zone adjacency rules to design safe workload connectivity paths?

Yes, zone adjacency rules define safe, policy-driven workload connectivity and external access paths. By applying the 2022 SDN Security Classification Model, you can establish compliant network boundaries and control data flow between different security zones.

How do I define egress policy guidance based on data classification?

Defining egress policy guidance requires applying the ISCF data classification framework to the workload. Based on the resulting Low, Medium, or High SDN zone assignment, the system generates actionable zoning decisions that specify internet egress constraints and 3PG connectivity requirements.

When do I need to reference the 2022 SDN Security Classification Model for zoning decisions?

You need to reference the 2022 SDN Security Classification Model when assigning workloads to SDN zones and planning compliant egress paths. It provides the current ISCF framework standards required to map data sensitivity to the correct OpenShift DataClass and network boundaries.