l5kit VS trivy

Level 5 | Self-driving Research | Palo Alto, US & London, UK & Tokyo, Japan | Full-Time + Interns | Onsite (Hybrid - 2 days in p/w - currently closed)

Level 5 at Woven Planet develops real-time car automation solutions via applied Machine Learning and Computer Vision (SFM, SLAM, 3D Perception etc). The system is adding self-driving capabilities to vehicles with the end goal of providing autonomy features to all cars from the largest car company in the world, Toyota. For more information please read through https://www.self-driving-cars.org

The platform at Level 5 is written in Python & C++. We are an AWS environment with additional use of NumPy, PyTorch, GRPC, Kafka, Kubernetes, Terraform, SageMaker, Spark, Postgres & others. We work in a OneBox cloud environment with continuous deployment and are firm believers in the benefits of open source (https://github.com/woven-planet/l5kit). We apply multiple flavours of ML to petabytes of data; such as Deep Learning, Transformers, Neural Networks & Reinforcement Learning. If you are interested in applying Machine Learning (ML) to real world data - look no further. https://www.self-driving-cars.org/datasets

If you like the idea of working on some of the most challenging problems in applied computer science. We are looking for talent across Data, Computer Vision, Machine Learning, Infrastructure, Research - and of course Software Engineering. Please find our jobs at https://boards.greenhouse.io/l5

4. Trivy: https://github.com/aquasecurity/trivy Trivy is a versatile tool that scans for vulnerabilities in your containers, and also checks for vulnerabilities in your application dependencies.

Trivy Owner/Maintainer: Aqua Security Age: First released on GitHub on May 7th, 2019 License: Apache License 2.0 backward-compatible with tfsec

Trivy. A Simple and Comprehensive Vulnerability Scanner for Containers.

Using Trivy:

Trivy is a mature and comprehensive open source tool from Aqua Security that supports scanning multiple sources, from file systems to containers and VMs. Trivy also looks beyond vulnerabilities, to scan licenses, secrets, infrastructure as code misconfiguration, and more.

I would suggest to think about the thread model that you are facing so you can have a better mental model of the weak points of your environment. The very very big majority of these attacks will be automated probing for publicly known vulnerabilities or default credentials. That means the maintainers of the software you are running and the channels on which their updates are shipped to you and deployed are very important factors. For software that is not installed from a trusted and well maintained source (e.g. Ubuntus main repository), you want to make extra sure that vulnerabilities are updated. E.g. your deployed docker containers might contain security issues, you can run checks on these with tools like trivy. The same is also true for appliances, in case your router or firewall contains a software vulnerability, how will you be notified and how will the required updates be deployed?