Obtaining an Automation Token
For operation-log syncing, prefer a scoped service token when the integration supports it. A service token can be limited to one operation log and its entries, so the automation does not inherit all permissions from the user who created the token. Use an API token only when the automation should act as your user account and inherit your current permissions. For custom logging tools, you can also consider using thelogin action with the API, but generated API tokens or service tokens are usually a better fit for long-running automation.
Read more about this process here:
Authentication
User Profile and Tokens
Setting up Syncing with Cobalt Strike
GitHub - GhostManager/cobalt_sync
Note: Cobalt Strike does not associate console output with the original command. Therefore, cobalt_sync cannot automatically complete the output fields for log entries. Job IDs may be available for CObalt Strike in the future.
Setting up Syncing with Mythic
GitHub - GhostManager/mythic_sync
Note: Since Mythic associates output with the original command, the mythic_sync project will retroactively update previous log entries when output is received. This will overwrite any additional context added to the original entry within Ghostwriter before the new output was received.