Getting Started with Container Scanning

container scanning helps ensure that the open source components that developers embed in their docker container meet basic security standards and do not introduce risk to the organization soos container scanning runs a proprietary, patented analysis engine which runs deep dependency analysis, license analysis, and vulnerability detection using our database of 84+ million packages getting started running a container image scan is quick and easy, once you have an account you can run a local scan or setup your ci/cd, from there you can add additional configurations and integrations scanning a container image cli or ci/cd integration use the containers tab of the integrations docid\ becfu au8wgt224lmm62g page to configure and run an container scan using a docker cli or ci/cd system how do container scans appear in the soos app? container scans will appear on your developer dashboad docid\ fhvqnychnq4kw2bmmnnin as projects project names can be specified using the cli or ci/cd integration if the project name corresponds to an existing project, the scan indicator will be used to show all scan types for the project see projects docid\ dxqzagmx rouuqu8lbent for more details on determining and switching scan types for a project technical readme want the technical details? check out or github readme it has all the details you'll need you can also browse the full source of our container cli under this same github repo, if you're curious! configuration the soos configuration system docid 5osexx1iyyvd unye3u7f provides a highly flexible and overridable configuration system integrations soos supports numerous integrations docid\ becfu au8wgt224lmm62g , including issue management integrations docid\ xfobdotvahwh1l6epafnq