You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenRelik is a forensic analysis workflow generation platform. This would be useful for us to be able to perform dynamic analysis on abstract packages; OpenRelik exposes an API which can ingest various files that would be generated by the dynamic analysis instance and perform analysis on them.
Timesketch is useful for timelining those results.
We should deploy these two instances in Kubernetes.
This Kubernetes instance (and related helm charts/infrastructure) should be considered a standalone project and entirely separate from Vipyr's main product.
It should:
Implement RBAC to the Kubernetes cluster for administrative purposes.
Preferably be simple to deploy (this will be useful for others.)
Use native Google OAuth authorization to the maximum extent possible to various services.
The text was updated successfully, but these errors were encountered:
OpenRelik doesn't have any deployment instructions for Kubernetes right now.
Also, their Docker Compose configuration seems geared towards deploying OpenRelik on a standalone machine with Postgres and Redis bundled as Docker containers.
OpenRelik also seems to be relatively newer than alternatives(?) like Turbinia.
There's an open issue in the OSDFIR Infrastructure repo for providing a Helm chart for OpenRelik.
Requirements
Implement RBAC to the Kubernetes cluster for administrative purposes.
We can extend the roles introduced with #39 for this new cluster.
Preferably be simple to deploy (this will be useful for others.)
I think a Helm chart with the Timesketch and OpenRelik Helm charts as dependencies will be simple enough.
Use native Google OAuth authorization to the maximum extent possible to various services.
I'm guessing you're asking for Google OAuth, because OpenRelik supports only that right now (other than "local" auth).
AFAICT, we'll need a Google Cloud project to use that, which we don't have right now.
Interest in contributing upstream at all for Github auth on OpenRelik? Everything else seems... reasonably straightforward I think.
@sid-maddy
Ref Turbinia, specifically looking at this as an easier-to-deploy known commodity ecosystem for shared analysis; this won't replace the modules concept, but augment a specific capability that we're probably lacking holistically, which is the ability to perform dynamic analysis and then collaborate on a standard set of information generated by this pipeline.
https://openrelik.org/docs/getting-started/
https://timesketch.org/guides/getting-started/
OpenRelik is a forensic analysis workflow generation platform. This would be useful for us to be able to perform dynamic analysis on abstract packages; OpenRelik exposes an API which can ingest various files that would be generated by the dynamic analysis instance and perform analysis on them.
Timesketch is useful for timelining those results.
We should deploy these two instances in Kubernetes.
This Kubernetes instance (and related helm charts/infrastructure) should be considered a standalone project and entirely separate from Vipyr's main product.
It should:
The text was updated successfully, but these errors were encountered: