Windows Console App vs Service

I would like to extend the question at the above post, as the previous answers did a great job of helping me understand the difference between a service and not a service.

The question I have now, is with applications that require to be up 24/7, what security concerns there are with a user that is logged in, vs the service not requiring a user to be logged into the machine. Obviously, if a user walks away without locking, that's an issue (and with redundancy, that's more than one vector of attack), but what other concerns should I be looking at to help my team understand that we're better off using a service for stuff that needs to be up 24/7?

Additional info, the core is on an SS7 network, with some functions migrating to IP (VoIP and mobile, for instance), so the focus of our security concerns are getting wider.

Windows Console App vs Service

I would like to extend the question at the above post, as the previous answers did a great job of helping me understand the difference between a service and not a service.

The question I have now, is with applications that require to be up 24/7, what security concerns there are with a user that is logged in, vs the service not requiring a user to be logged into the machine. Obviously, if a user walks away without locking, that's an issue (and with redundancy, that's more than one vector of attack), but what other concerns should I be looking at to help my team understand that we're better off using a service for stuff that needs to be up 24/7?

Additional info, the core is on an SS7 network, with some functions migrating to IP (VoIP and mobile, for instance), so the focus of our security concerns are getting wider.