Hi all,

We were looking to uniquely tag a scan with some sort of ID that would allow us to map it back to a client...something like a session id or something else. The first idea we came up with was to simply set an iterator option that could be viewable in listscans in the shell. Basic idea would be to map it back to more than just the IP address of the client (e.g a user name or something else injected on the client side for a client servicing multiple users).

Wondering if anybody else had done this before or if there were any thoughts about having "scan metadata" in the future?

Thanks,

Andrew

Reply via email to