GitHub - opencybersecurityalliance/interoperability-village (original) (raw)

Village

🌐 Introduction

In an era of increasingly complex security ecosystems, no single tool can stand alone. Interoperability is essential—and yet testing often happens in isolation, constrained by proprietary infrastructure and limited collaboration. This project breaks down those silos

Our mission: enable real-world, hands-on interoperability testing through a flexible, distributed, and community-supported lab architecture.

The IoV serves as a vendor-neutral playground for:

🌐 What is the Interoperability Village?

The Interoperability Village is a federated ecosystem of virtual test labs—called Neighborhoods—interconnected over secure, decentralized virtual networks. Within each Neighborhood, participants can spin up modular environments called Huts, where individual tools and platforms are deployed, integrated, and tested together.

🚀 Project Overview

The Interoperability Village (IoV) is a sub-project of the Open Cybersecurity Alliance (OCA), under the **Cyber Automation Sub-Project (CASP).

🎯 Core Objectives

🧪 Key Use Cases

⚙️ Build. Break. Iterate. Interoperate.

🧰 Core Use Cases

🧱 Architecture Overview

Each participant connects through a Headscale-powered decentralized Tailscale network, enabling seamless and secure Layer 3 connectivity across disparate environments without needing to expose public IPs or configure firewalls.

🏡 Architecture: "The Village"

🧱 Neighborhoods & Huts

You bring your public IP and ACL, we provide an Agent Provisioning Script. That’s it.

🧰 Hardware & Tooling

We've had excellent results using:

Supported Frameworks

If it runs in a Docker container, it runs in IoV.

✅ Key Components

🔒 Why Headscale?

🛠️ How to Participate

🏘️ Request a Neighborhood

Want to run your own Interoperability Village site?

Submit a GitHub issue or email interoperability@opencybersecurityalliance.org with:

name: "My Neighborhood Name" organization: "Org Name (if applicable)" maintainer: "Your Name and GitHub Handle" use_case: "Short description of your tools or focus (e.g., OpenCTI and OpenC2 translation)" preferred_location: "Optional - e.g., AWS us-east-1, self-hosted, etc."

We will provision:

🛖 Request a Hut

Already part of a Neighborhood and want to spin up a new Hut?

You can:

Example Hut types:

🤝 Join the Conversation

Let’s build the future of cybersecurity—together. You can join the OCA Interoperability Village mailing list by sending an empty email to oca-interop-village+subscribe@lists.oasis-open-projects.org .

You can join the OCA Slack via this link. There is a #interoperability-village channel :).

List the current project maintainers, and their Github user IDs

Patrick Maroney packet-rat

🗓️ Community Engagement

To grow the Village, we focus on:

📜 License

This project is licensed under the Apache 2.0 License.
See LICENSE.md for full terms.

🧭 Get Involved

🔧 Ready to Build a Neighborhood?

Drop your public IP and request your provisioning script!

Build your 'Huts', test your tools, and join a growing community shaping the future of cybersecurity interoperability.

📈 Provisioning Flow

Interoperability Village Provisioning Flow

🧪 Testbed Topology

flowchart LR subgraph "Headscale Mesh Network" A[Neighborhood: Vermont] --- B[Neighborhood: California] A --- C[Neighborhood: Europe] B --- D[Neighborhood: Asia-Pacific] end

subgraph A [Neighborhood: Vermont]
    H1[Hut: MISP Node]
    H2[Hut: OpenCTI]
    H3[Hut: OpenC2 Proxy]
end

Loading

🧪 Plug-and-Play Testing