The Zetafence Story


Born out of frustration in designing modern Dev / SecOps workflows for brownfield & greenfield deployments in earlier lives.

  • Dependency evaluation requires sophisticated tools.
  • Though underlying infrastructure was sophisticated, there were no elegant ways for operators to develop critical decision-making logic best suited for their needs. Operators should focus on workflow design, not how to enact them.
  • Operators always needed integrations and customization - filters, priorities, actions of what alerts are important to react faster.
  • Alerting, logging primitives are basic today e.g. Slack app, Alert logs, Email, etc.

Thus, Klig.io was born in 2022 primarily with the intention of easening Dev & DevSecOps, which transmogrified into Zetafence.

Here is a summary of how Zetafence ideas was originally conceived, and developed.

  • Graphical abstraction was naturally perceived an important aspect from beginning. Graphs provided a very intuitive way to represent abstract entities, and relationships between them, and be able to validate analytically.
  • Not just any graph, but Hypergraphs. Hypergraphs are equivalent to unveiling multiple dimensions of the same problem e.g. 2D vs 3D, and offered to reveal granular details that otherwise would create blindspots.
  • Blindspot detection in security was perceived to be important in security analysis. This was particularly appealing to analyze using Hypergraphs. An equivalent example is map application in NYC showing various connected points via roads, but tunnels offer a completely alternate and richer perspective.
  • Building out Hypergraph abstraction semantics enabled to change perspective of the problem domain, and observe existing problems in in a completely new way. For instance, viewing dependencies and relationships among Kubernetes resources such as ClusterRole to Deployment could be vastly enriched via Hypergraph representing ClusterRole to Deployments + Namespaces.
  • Set theory was favorably related and proved extremely useful and simple to represent Hypergraph relationship associations & modifying them.
  • Building out a management plane particularly using Hypergraph resulted in building out resource control operations from ground-up, which enabled a refreshingly new perspective in dependency analysis, queries, etc.