>Of course there's a chance that this user account may end up getting deleted during the course of a security audit (I'd seen this happen on a few occasions). To reduce the chances of this happening, it probably would be a good idea to make sure that such an account have a meaningful description (e.g. "username used by automation task for ___ application") rather than being left blank. This of course assumes that the person(s) doing security audit don't start blindly deleting user accounts that don't seem to be associated with live persons (which I have seen on at lest one occasion).

Security audits are a special kind of circus. My team was though two such events, consecutively, at a client, and we were asked about "why is Foxit installed?" - "because Acrobat is too big and we produce pdf documents which we need to check from time to time" and such shit. Yet neither audit found my TotalCommander, because I never installed it. I just unzipped my own installation in a ...\ourApp\backup\tc folder and didn't create a shortcut for it, just ran it with win+R key, which is so rarely used that it never dropped off the MRU list :). And two audits (second one because they didn't like the team who did the first) didn't find it in the registry, didn't check other places, all good. It's still there, diligently and unwittingly migrated to third server now, after twelve years.

And ah, yes, they never checked that MRU list either.