WABBALABS
Solutions

Concrete use cases, from the microsegmentation project to day-to-day operations

Wabba-Sego answers the situations that teams deploying and running Illumio Core meet every day.

Leave visibility only behind

The situation: Workloads stay in visibility only: nobody knows what a move to enforcement will block.

With Wabba-Sego:

  • Compatibility reports checked before leaving idle mode.
  • “Potentially blocked” flows shown at the dry run of a move to selective or full.
  • Allow rules listed for every workload; acknowledgement for a move to full with no rule.

The result: Gradual enforcement, plan after plan, with every step measured.

The features involved

Handle flow opening requests

The situation: Requests arrive as IP addresses; an expert must translate them into label-based rules, in the right place.

With Wabba-Sego:

  • Each address resolved into a workload and its labels; flows already open detected.
  • The rule built following your conventions and checked against your guardrails.
  • Up to 100 flows per file; a request file to attach to the ticket.

The result: Requesters keep their habits; the expert reviews instead of re-keying.

The features involved

Change without cutting production

The situation: A label, a mode or a rule that changes alters the flows; outages are discovered in production.

With Wabba-Sego:

  • Impact calculated before writing: flows cut and opened, immediate effect flagged.
  • Proposed rules keep the flows a change would cut, written before the rest of the plan.
  • The plan is outdated if the PCE's state has changed: nothing is written.

The result: Predictable changes, approved with full knowledge of their effect.

The features involved

Prove compliance

The situation: Audits, NIS2, DORA, ISO 27001: you must show that the policy meets the requirements, and since when.

With Wabba-Sego:

  • A PDF compliance report per instance, with a risk score and recommendations.
  • Registers of exceptions and recertification; audit and exchange logs.
  • Guardrails checked wherever a rule is created.

The result: Evidence ready, and deviations corrected as you go.

The features involved

Clean up and keep the policy in shape

The situation: Unused, too broad or duplicated rules pile up; labels drift from the reference.

With Wabba-Sego:

  • Rules with no hits, or no workload left, found even with no traffic.
  • Remediation in a single plan, in an order designed not to cut anything.
  • Every rule recertified when due.

The result: A granular, least-privilege policy that stays that way.

The features involved

Industrialise your managed services

The situation: Every customer has its own conventions; MSSP teams juggle consoles and scripts.

With Wabba-Sego:

  • One tenant per customer, kept apart, with several PCEs if needed.
  • Each customer's model, conventions and guardrails configured, with no development.
  • Roles, four-eyes approval and logs per tenant.

The result: Governance that is repeatable from one customer to the next.

The features involved

Benefits

What everyone gains

  • CISOs and management

    • Compliance that is measured and proven: report, registers, logs.
    • Your guardrails checked wherever a rule is created; every exception dated and traced.

  • Network and security teams

    • Requests handled with hardly any change to your processes: rules built and checked.
    • Fewer incidents: impact calculated and rules proposed before writing.

  • Integrators and MSSPs

    • One platform for all your customers, kept apart.
    • Each customer's governance, applied in a repeatable way.

Try Wabba-Sego on your infrastructure

  1. Demonstration

    On your use cases, with your conventions.

  2. 90-day pilot

    Installed on your premises, offline, connected to your PCE: a pilot on a real scope.

  3. Pilot review

    From the labelling model to enforcement: objectives set at the start, measured at the end.

Request a demonstration Start a 90-day pilot