@ap This is true however, as the official standards say something to the affect of; they do not care how long you stay onsite as they believe in "flexibility." Meaning, if you want to work onsite for 10 minutes, you can. If you want to work onsite for 8 hours, you can. Obviously this is dependent on your manager as well but, the guidelines are quite clear.
As someone who has full access to the VPN's... It's not quite as cut and dry as you think it is in regards to monitoring. We can see who connects to VPN at what time and, can see who disconnects from the VPN at xyz time. We can see what public IP you are connecting from/as but, that's about it.
Pretend you go into the office, sit down, connect your system up to the dock, then login to your VPN. You'll get an internal IP address that is part of the VPN IP address pool. A xx.xx.xx address or xx.xx.x-x address. So now, you have proof you are connected to the VPN as well as having a "public IP" which would be a Dell IP since you either connected via wire or their dogcrap WiFi.
OK so, now it's lunch time and you decide to go to Chilis. You take your computer with you and reconnect via Chilis wifi. You will get disconnected from the VPN as soon as you leave the wifi radius and, will then get a new public IP from the Chili's WiFi. Because you are now connected from a new location, when you login to the VPN, you'll likely get a brand new IP address as well.
Now, you go back to office reconnect, and then 2 minutes later are having issues with connections. So, you then go setup shop in the cafeteria. You connect to wifi and VPN but, it's not working well there either! So at this point you say fk it and decide to go home but, remembered you have a meeting you need to be in. So you connect to your phones hotspot, reconnect to the VPN and attend that meeting on your drive home.
Then you get home, hook your stuff back up and reconnect to the VPN.
In that single theoritical day, you disconnected/reconnected to the VPN FOUR times. Do you realize how much of a mess it would be to accurately track who is on VPN AT a dell office? VP's/C levels/directors/managers don't actually have access to the VPN's, btw.
To break it down in simple terms... and as a very real example...
User: logs into VPN at 8:07am - public IP is a Dell IP
User: disconnects at 11am
User: reconnects to VPN at 11:23am - public IP is non- Dell (chilis)
User: reconnects to VPN at 1:03pm - Dell public IP
User: disconnects from VPN at 1:10pm (connection issues)
User: Reconnects to VPN at 1:15pm (Dell public IP again)
User: Disconnects from VPN at 1:20pm - Public IP unkown (phone hotspot perhaps)
User: reconnects to VPN at 2PM - public IP is Spectrum (likely at home now on their own internet)
My point here is that, it's basically impossible to track who is at a Dell office and for how long. Technically, not impossible but it's a FAR more work to have cyber spend much of their time deciphering who was where, at what time, and what fkng public IP they have when connected to the VPN lol...
Trust me on this one, the last thing SRO VP's care about is prioritizing who was where, at what time, and how long they were connected...
Fun story though: Years ago, I was contacted by an SVP, VP, and a Sr. Director asking me to give them logs of a certain person's VPN connectivity. I immidiately told my manager because of their titles and was told "give em what you can." So, I went and pulled their VPN logs and it was pathetic. Over a MONTHs time period, I think he was connected to the VPN for roughly 20 hours lol. I put it all into a spreadsheet with the every day he connected, when he disconnected, if he even connected at all, etc... and sent that to them.
I told my best friend about this who also worked at Dell and he said "wait, WTF?? I work with this dude lol!" The guy ended up being fired. I still feel somewhat bad about this because I unkowngly got someone fired..