Goverment officials are required to archive all communications, so it doesn’t defeat the purposes of E2EE because you can’t have full E2EE to start with. If it was propely implemented and didn’t get hacked it would be fine. Tho I guess implementation wise if it really sends all the data to a corporate instead of government cloud that’s a problem as well.
If it was propely implemented and didn’t get hacked
If it was properly researched and approved by DoD and used on authorized, secure devices which were running on secured networks, it would be fine.
The baseline for security has been pretty decent for years. It’s painfully restrictive which is why they’re chomping at the bit to make it easier, but just slamming a corporate product into use with secret data with no oversight has never been fine even if it was secure.
Goverment officials are required to archive all communications, so it doesn’t defeat the purposes of E2EE because you can’t have full E2EE to start with. If it was propely implemented and didn’t get hacked it would be fine. Tho I guess implementation wise if it really sends all the data to a corporate instead of government cloud that’s a problem as well.
If it was properly researched and approved by DoD and used on authorized, secure devices which were running on secured networks, it would be fine.
The baseline for security has been pretty decent for years. It’s painfully restrictive which is why they’re chomping at the bit to make it easier, but just slamming a corporate product into use with secret data with no oversight has never been fine even if it was secure.