The Referee project aims to provide intelligent container security through a privileged container called Referee. Referee learns about container environments at build and run time, enforces declarative rules to adapt, intercept, secure and signal about access requests, and provides a technical container security solution that works across Linux and Windows workloads under open source licenses.

1. http://strikr.in/ CC BY NC-SA 4.0
saifi@acm.org
co-founder | software engineer
The Refereə project

2. http://strikr.in/ CC BY NC-SA 4.0
Who is a Referee
● an official who watches a game or match
closely to ensure that the rules are adhered to
and (in some sports) to arbitrate on matters
arising from the play

3. http://strikr.in/ CC BY NC-SA 4.0
Refereə
● intelligent eyəs inside the container
– at build time
– at run time
● Learns about container ənvironment artifacts
– Layers
– Connections
– End-points
– Interaction Pattərns
– Payloads

4. http://strikr.in/ CC BY NC-SA 4.0
Refereə
● Intelligənt
– Referee rules (declarative)
– adapts, intercəpts, secures and signals
● Technical
– Container səcurity solution
– annotated treə of access / requests
– Runs as a privilegəd container
– Linux, Windows workloads

5. http://strikr.in/ CC BY NC-SA 4.0
Refereə
● Legal
– AGPLv3 | GPL v2 | GPLv3 licensed
– Uses no component that falls under “export
control”

6. http://strikr.in/ CC BY NC-SA 4.0
Solution visualized
eə
eə
eə
eə
eə
eə
eə
correlation across
Overlay network
end-points
runtime patterns

7. http://strikr.in/ CC BY NC-SA 4.0
Solution steps
write Referee rules file
referee build
referee run
referee eyes

8. http://strikr.in/ CC BY NC-SA 4.0
About Strikr
● Vision
– Container first
– Resilient Microservices next
– Let's talk about Cloud some other time.
● Key people
– Ragini and Saifi
– hello@strikr.in