It's a platform problem. The cross-availability of information on let's say ... Google Android. They can use a microphone, wifi signal analysis, and other techniques that make your GPS coordination data moot. What's getting more complex is the data itself, and how it be sorted and moved around the need for actual location data. That's why I think the "disable GPS / Location" actions in Android (and macOS) needs to be more granular. When we say "don't track me" .. it means ... on everything and protect the information from software in silos. It goes against the grain of security vs. usability .. but its gonna happen by will of the people.
I believe it covers sensitive materials only. Soldiers should not be punished through UCMJ for using Strava. That's ridiculous. Strava just should not be accessible within Afghanistan.
So let me ask you .... how do IT folks actually handle this type of situation? The experience required for systems work both in the field and base are both between making soldiers at home, in combat zones, and also keeping them safe. It's something that requires a LOT of experience on new tech to really stop/filter/protect against situations where data is being transferred off base. There is also the STORED perspective. That data may not be transmitted ON base .. it could be transferred over a wifi at something like the "sister's house" or some other place you never expected on an open network for wifi with that device. It's nearly impossible to stop this. It's like White House leaks .. when there is a way to transmit, it will be used.
