# Vulnerability scanner as a service for linux devices using syft

**URL:** <https://anchorecommunity.discourse.group/t/vulnerability-scanner-as-a-service-for-linux-devices-using-syft/658>\
**Category:** Syft\
**Created:** [August 18, 2026, 11:40am UTC](https://anchorecommunity.discourse.group/t/vulnerability-scanner-as-a-service-for-linux-devices-using-syft/658 "2026-08-18T11:40:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hriday\_Pradhan](https://yyz2.discourse-cdn.com/free1/user_avatar/anchorecommunity.discourse.group/hriday_pradhan/32/471_2.png) [@Hriday\_Pradhan](https://anchorecommunity.discourse.group/u/Hriday_Pradhan)\
**Post date:** [August 18, 2026, 11:40am UTC](https://anchorecommunity.discourse.group/t/vulnerability-scanner-as-a-service-for-linux-devices-using-syft/658/1 "2026-08-18T11:40:57Z")

</div>

Hey everyone!

I came across Syft while exploring options for a project I’m working on and it seems like it could be a great fit. Would appreciate any guidance or pointers to existing threads!

Use case: We’re building a vulnerability scanner as a service for Linux devices, and Syft is on our radar as a potential core component for this.

A few things we’ve run into or are thinking about:

1. RAM utilization: We noticed some concerns here and would love to understand if there are ways to optimize or tune this for our setup.
2. Scan scope adjustment: Since we won’t always know the exact configuration of a customer’s device upfront, we’re wondering how flexible Syft is when it comes to narrowing or adjusting the scan scope dynamically.

Thanks in advance!