Some payloads coming from Atomic Red team are marked as "Manual"

[SamuelHassine]

Description

https://filigran.obas.filigran.io/admin/payloads

Should be "community"

[savacano28]

On staging we have the correct source: https://testing.obas.staging.filigran.io/admin/payloads?query=cGFnZT0wJnNpemU9MTAwJmZpbHRlckdyb3VwW2ZpbHRlcnNdW10mZmlsdGVyR3JvdXAlNUJtb2RlJTVEPWFuZCZzb3J0cyU1QjAlNUQlNUJwcm9wZXJ0eSU1RD1wYXlsb2FkX25hbWUmdGV4dFNlYXJjaD1TY2hlZHVsZWQlMjBUYXNrJTIwUGVyc2lzdGVuY2UlMjB2aWElMjBFdmVudHZpZXdlci5tc2Mma2V5PXBheWxvYWRz

So, we need validate the openbas version for https://filigran.obas.filigran.io/admin/payloads and also collector atomic red team version

[johanah29]

Hello @EllynBsc and @jborozco
After investigation, it turns out that the payloads mentionned earlier do no longer exist in the atomic red team folder. We now need to figure out what we should when such an event happens. We have three options:

• Delete the payload from the database
• Keep the payload with a "deprecated" or "no longer exist" flag
• Keep things unchanged

[EllynBsc]

Hi @johanah29 👋

2 solutions here IMO:

👉 Solution 1: Keep the payload with a "deprecated in version XX" flag, i think it's important to state to our user that it's deprecated in the current repo version of Atomic Red Team we're using but it might not be the case in a previous version.

👉 Solution 2: Delete the payload from the database, IMO it's not useful for the user to end up on a payload that does not exist in the atomic red team folder. And we should also specify what version of Atomic red team we're using.

=> I'd say we go for solution 1 for now, and then if we realize that atomic red team updates a lot and we end up with a ton of payloads deprecated then we can put solution 2 in place. WDYT ?

[jborozco]

@johanah29 @EllynBsc Hello, I would say let's delete the payload to make sure our offer is reflecting functioning payloads.

[EllynBsc]

Hi @jborozco 👋

Good for me!