Idea: Server Provider Import

[kkirsche]

This idea is to add tasks which allow the automated import of servers from one or more providers, such as:

• AWS
• Digital Ocean
• Google Cloud
• vSphere on Premise

etc.

This would allow the server page to stay up to date without the need for manually importing.

[chrismaddalena]

Off the cuff: I can see this being feasible if it there were a way to link the projects. You'd probably have to commit some sort of tag or keyword to be used between all environments/platforms. I know AWS and DO APIs will let you add tags, but I don't know about the others.

I like the idea.

[er4z0r]

So from what I can see this is already somewhat implemented, yes? I tried importing servers from DO, automated task (ghostwriter.shepherd.tasks.review_cloud_infrastructure) completed successfully, retrieved some servers, but for some reason they are not shown in the server manager.

[chrismaddalena]

@er4z0r The server library can be confusing in its current iteration. The goal was to offer a way to manage persistent/static servers–i.e., servers you/your team own, maintain, and reuse. These are servers you might use for command and control (e.g., Cobalt Strike's Team Server, Mythic C2 controller) or dedicated hash crackers.

Similar to domains, it's a way to let everyone else know you are using that shared resource until a certain date.

Everything from the cloud is stored separately on a per-project basis. If you spin-up a temporary server to use as a redirector or web host, you can track that under a project. Those aren't shared resources so they don't need to be tracked in the library for check outs.

Of course, every team is different. If all your servers are cloud resources then the difference becomes muddy.

You are right that the cloud monitoring task is already pulling the cloud server info. The idea here is to switch from alerting you of an untracked cloud resource to automatically tracking it for the proper project (if possible).