Remote security issues re not locking server screen

[Bluecube]

My server runs a couple of apps that don't take well to sitting behind a Lock screen. The server runs 24/7 with net access so security is quite important. Normally, I remote login to do whatever needs done then Lock the screen but due to aforementioned apps I can't do this.

Which is all a long winded way of asking what sort of security issues will I open myself up to by not Locking the screen...

[peterb]

What is the server OS?

You should really run all applications as background jobs, and then log off completely. I run a Linux based server that doesn't need a monitor, keyboard or mouse connected, but if anyone did connect those, they would be presented with a login prompt at a command line interface.

Running logged in is in itself a security risk, if that logged in account has administration privileges then anyone with physical access to the computer has access to everything. A screen lock gives you some protection, which is better than none.

But unless you have whole disk encryption (or at least data store encryption) then anyone with physical access to the machine can just take the machine or drives and analyse them at their leisure.

[Bluecube]

Windows Server 2012 R2. Practically all the apps I run won't run as services (unless I'm missing something obvious) hence the need to be logged in. I take it that's what you mean by running them as background jobs?

There's nothing inherently valuable on the server but I'd rather not have anyone and everyone raking through it. If someone accessed it physically then it means someone's broken into my house so it'd be the least of my worries!

[Splash]

What are your problematic apps?