'Lab/Testing/Engagement' tags would be helpful in allowing for organization of beacons. I often find that Posh is exclusively used with a test environment alongside a real-world project/engagement
Tags would then in theory allow for ;
Pooling logs. Eg Test environment tags could feed into a separate logs to that of beacons with an 'engagement' tag. Avoiding cross-contamination and economizing workflow when searching through logfiles.
Greater 'Dashboard' control. Meaning that you could selectively view logs specific to a certain tag (Eg the command 'Posh-Log 'Testing' would tail the aforementioned pooled log as opposed to the meta-log file that currently exists), and similarly only view or at least be able to organise implants of a specific tag. (In a similar way to how the -a argument works when logging into posh only shows you beacons that are alive)
Tagging Beacons/Implants
'Lab/Testing/Engagement' tags would be helpful in allowing for organization of beacons. I often find that Posh is exclusively used with a test environment alongside a real-world project/engagement
Tags would then in theory allow for ;
Pooling logs. Eg Test environment tags could feed into a separate logs to that of beacons with an 'engagement' tag. Avoiding cross-contamination and economizing workflow when searching through logfiles.
Greater 'Dashboard' control. Meaning that you could selectively view logs specific to a certain tag (Eg the command 'Posh-Log 'Testing' would tail the aforementioned pooled log as opposed to the meta-log file that currently exists), and similarly only view or at least be able to organise implants of a specific tag. (In a similar way to how the -a argument works when logging into posh only shows you beacons that are alive)