Generate partial YARA rules for give executable in RESTful4Up

What this operation does

generate partial YARA rules for give executable.

• POSTChanges datarestful4up.local/generate-partial-yara-rules

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which RESTful4Up operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other RESTful4Up operations

• Try to unpack the given filePOST · changes data
• Try to get the emulation output after unpacking the filePOST · changes data
• Apply given YARA rules to the given executablePOST · changes data

All 4 RESTful4Up operations

Questions

Can HumDay generate partial yara rules for give executable in RESTful4Up?

Yes. This operation is published in RESTful4Up's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my RESTful4Up data?

Yes — this is a POST operation, so it changes something in RESTful4Up. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your RESTful4Up account.

Where this came from

Read from a published API description for RESTful4Up at raw.githubusercontent.com/rpgeeganage/restful4up/master/app/spec/api.yml. The description above is the provider’s own wording, not ours. Last published 2021-06-21.