Updated Falco Roadmap (markdown)

Mark Stemm 2017-03-29 16:40:25 -07:00
parent 5e4f391d6b
commit a465d0d761

@ -1,4 +1,4 @@
Here's a sketch of the features we're planning on adding to Falco in the next several releases. When relevant, we've included links to the relevant github issues. Afterward, we'll list the specific features we're planning on adding in the next Falco relase (0.6.0). Of course, plans may change, but this should give you an idea of what's on the roadmap for Falco. If you see specific features you're especially excited for, or if you have features that you'd like to see that aren't on this list, let us know!
Here's a sketch of the features we're planning on adding to Falco in the next several releases. When relevant, we've included links to the relevant github issues. Afterward, we'll list the specific features we're planning on adding in the next Falco relase (0.7.0). Of course, plans may change, but this should give you an idea of what's on the roadmap for Falco. If you see specific features you're especially excited for, or if you have features that you'd like to see that aren't on this list, let us know!
# Overall Roadmap
@ -23,14 +23,12 @@ Here's a sketch of the features we're planning on adding to Falco in the next se
* Flight data recorder--when a rule triggers, save the last N events to a trace file. [[#81](https://github.com/draios/falco/issues/81)]
## Misc
* Clean up the ordering of dependencies when building from source. [[#130](https://github.com/draios/falco/issues/130)]
* Add container-based tests that ensure that the built containers actually work. [[#188](https://github.com/draios/falco/issues/188)]
* Add the ability to test the falco ruleset and exit [[#194](https://github.com/draios/falco/issues/194)]
# 0.6.0 Planned Features
# 0.7.0 Planned Features
* Add a rules.d directory where people can drop in rule files.
* Add rules that highlight k8s/mesos support.
* Add rules that implement as much of the CIS Docker benchmark as possible in falco.
* Break existing ruleset into separate pieces and add ability to enable subsets of them individually (A rules.d directory would make this much easier).
* In the repository add puppet/ansible/k8s daemonset/mesos application configs that make it easy to deploy falco.
* Clean up the ordering of dependencies when building from source.
* In the repository add puppet/ansible/k8s daemonset/mesos application configs that make it easy to deploy falco.