-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate Witness, Falco, Tracee, Cilium, etc. for demo of runtime visibility #212
Comments
I would like to have a better understanding of how were can interrogate Cillum and Falco to generate attestations. witness knows the PID and all of the metadata for the CI process @fkautz do you have any implementation ideas? |
We can look at pulling information from cilium and Falco and use them in the attestation process. Normalize, correlate, and sign the information gathered. e.g. should be possible to capture network policy configuration, connection information, and other relevant info and correlate with the information traced by witness. Would need some work to gather and perform the correlation, but would give us the ability to look for anomalies. |
@mlieberman85 how do you see cilium fitting in? |
Option 1Falco has a GRPC API that we can connect to over UDS. This seems like a good fit. I think we can hack in some code to connect to the Falco API to listen to events happening in the system when the commandrun attestor is working. Option 2I'm not sure if this will work, but may fit in better with witrness' model. Create a Falco Source Plugin. that filters events we care about for witness. We can then communicate these events to witness using a postrun attestor. |
Hi everyone! This is awesome :) I was in the process of trying to build a Kubernetes tool that can create 'Falco Attestations' in a similar way to what is discussed here. I would love to talk about this more and understand how Tracee, Witness and Cilium all ties in. |
https://github.com/cilium/tetragon seems like a good fit for integration with witness. I added an issue here: in-toto/witness#186 |
SSF is an implementation of Secure Software Factory Ref Arch as shown above. A gap we currently have is in runtime visibility space. We should explore various runtime visibility (tracing, eBPF) tools to see how we could integrate them into SSF.
Common ones to explore are:
SSF is intended to abstract out underlying implementations but we do want to explore which ones might be easiest to integrate for the default.
The text was updated successfully, but these errors were encountered: