Let me answer as this is an enhancement that as driven by myself.
We poll for the summary and page in the data we get, parsing this and writing it into our Endpoint DB, we then make secondary calls for every endpoint for more security/policy specific attributes. Their are SIX TAGS in the device XML we get,
IsCompromised
DataProtectionEnabled
BlockLevelEncryption
FileLevelEncryption
IsPasscodePresent
IsPasscodeCompliant
Now one of these XML TAG attributes <IsCompromised> is also available in the summary poll, its called <CompromisedStatus>.
So by not polling for the security data we save a HUGE amount of extra polling but we do lose the ability to have certain endpoint attributes data available to be used by CPPM in its enforcement process.
But, I've had a number of very large customers 75K+ devices who don't care about the security data but do care about the large overhead of the secondary polling, plus it absolutely kills Airwatch servers.
HTH