Skip to main content

Hide dynamic assets

The assignment of an owner for dynamically generated assets is not useful. We would like to be able to hide the dynamic assets from the asset inventory.

Status: Complete6 comments

Log in to comment and vote

Comments6

  • Grigory Emelianov changed status to Complete
    Team•

    Jul 18, 2023

    Done! Starting from the last we you're able to use Cloud Bulk Tagging to hide dymanic(cloud) assets. We hide all the assets that are tagged with SecfixNoAlert or SecfixNonProd = true. You can learn more here: https://help.secfix.com/en/articles/8061789-how-to-automate-cloud-inventory-documentation-via-bulk-cloud-tagging

  • Grigory Emelianov changed status to Under Review
    Team•

    Apr 4, 2023

    We are starting to research this problem

  • Grigory Emelianov

    Team•

    Mar 30, 2023

    Thank you Rene! Quick follow-up question: Do you utilize Terraform or Cloudformation (or any other IaaC scripts) for Jenkins bot to create the aws assets with tags inside? Also would every cloud asset have the same owner or would it change on specific assets/cloud categories?

    • René M.

      •

      Mar 30, 2023

      Grigory Emelianov: probably all cloud assets will be assigned to the same devops responsible. but we have two clouds, one for our development (not fully scripted) and one for our saas-clients (all with terraform). but we have tags already, yes!

  • Grigory Emelianov

    Team•

    Mar 30, 2023

    Hey Rene, nice to feedback-meet you :) Could you elaborate why assigning of an owner to automatically synced assets is not useful?

    • René M.

      •

      Mar 30, 2023

      Grigory Emelianov: this is due to the ephemeral nature of dynamically generated assets. e.g. the jenkins bot creates and destroys aws assets several times a day. there is no meaningful way to treat such short-lived assets in an appropriate manner (owner, description). so just hide them.