Overview

At OPSWAT, a critical-infrastructure cybersecurity company, I worked as a product designer across four enterprise products — My OPSWAT, Central Management, MetaDefender Drive, and Industrial Firewall — designing complex, technical workflows into interfaces that security and operations teams can rely on every day.

The context

OPSWAT secures the files, devices, and data transfers that move into the world's most critical networks — energy, manufacturing, defense, and other operational-technology environments. Designing for this space means designing for technical users making high-stakes decisions, often across distributed, on-premises, and even fully air-gapped sites.

The work spanned dense administrative dashboards, multi-step security workflows, and constrained on-device interfaces. Across all of it, the constant was the same: make complex security information legible and trustworthy, and keep four distinct products feeling like one coherent system.

What I worked on

Four products, each with a different surface and a different kind of user:

  1. My OPSWAT

    The unified customer portal for license management, product downloads, and role-based access — a single pane of glass for an organization's OPSWAT products.

    Design focus

    Account & licensing flows, role-based access, onboarding, and at-a-glance status, customer support experience flow.

  2. Central Management

    The centralized console for managing every MetaDefender instance: policy enforcement, near-real-time health monitoring, and updates across cloud, on-premises, and air-gapped sites.

    Design focus

    Data-dense dashboards, policy configuration, and multi-instance information architecture.

  3. MetaDefender Drive

    A portable bare-metal scanning device that inspects laptops and assets before they boot, with an on-device screen and report syncing for isolated environments.

    Design focus

    On-device UI for a small screen, scan-result clarity, and constrained-hardware UX.

  4. Industrial Firewall

    A ruggedized firewall for OT networks that protects industrial control systems through zone-based segmentation and protocol-aware deep packet inspection.

    Design focus

    An OT-friendly dashboard surfacing system status, policies, and rules for industrial operators.

How we worked

My process ran from early requirements through implementation:

  1. Requirement gathering

    Partnered with PMs to translate product and security requirements into clear design problems.

  2. User flows

    Defined end-to-end flows for complex, multi-step security and management tasks.

  3. Technical alignment

    Worked with engineers early to align designs with platform and technical constraints.

  4. Design system

    Maintained and extended the shared design system to keep four products consistent.

  5. UI & handoff

    Delivered final UI and edge cases, then handed off and supported the build.

  6. Iteration

    Refined flows and components based on feedback across releases.

Working across a multi-product security suite taught me to design for clarity and trust over decoration, to treat technical and environmental constraints as the real brief, and to use a shared design system as the thing that keeps a large, complex product family coherent as it grows.

Selected screens

Fig 1. Snippet of Site Analytics feature in My OPSWAT Admin Portal
Fig 2. Snippet of Vulnerability Disclosure feature in My OPSWAT
Fig 3. Snippet of Customer Health Dashboard feature in My OPSWAT Admin Portal

Takeaways

Clarity over flash

In security tooling, an interface earns trust by being legible and predictable, not decorative.

Constraints are the brief

Air-gapped sites, small device screens, and OT operators each reshape what “good” UI means.

Systems keep products coherent

Maintaining the design system was as much product work as any single screen.