4 ms·
> While account IDs, like any identifying information, should be used and shared carefully, they are not considered secret, sensitive, or confidential informati
by cj 3y ago
> While account IDs, like any identifying information, should be used and shared carefully, they are not considered secret, sensitive, or confidential information.
https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-identifiers.html https://docs.aws.amazon.com/accounts/latest/reference/manage...
- dimitrios1 3y agoSeems like at least in the digital world, there is either public or private information, and that's it. We don't really have a good concept of privilege or protected information. For example, my home address is technically public, but I most certainly wouldn't want it lambasted across the interstate with a picture of my family next to it advertising where I live. It's handed out on a need-to-know basis, and I mostly trust / expect that it's kept mostly confidential, or use-limited.
- greiskul 3y agoOne huge mistake that Google did when they were integrating youtube with Google+, was the idea of sharing people's youtube comments with their G+ friends. Youtube comments have always been public, but there was huge customer pushback, forcing them to revert them for this idea, since there is in people's mind a huge difference between public and publicized comments.
- styfle 3y agoAlso G+ made your email address public to your friends/circles/etc and I don’t think there was a way to disable it.
- mellutussa 3y agoYep, that and other things like reviews wm you did went straight to your Google+ page. I really wanted G+ to work, but they were just too stupid to understand that this was a deal-breaker.
- panarky 3y agoWhat does this mean? If they're not secret, sensitive, or confidential, then why must they be shared carefully?
- pyre 3y agoThere is plenty of information that you wouldn't necessarily want to publish, but wouldn't be the end of the world if it were leaked either.
- rmbyrro 3y agoUsually, the more information an attacker has about you, the higher the chances of coming up with a successful attack vector.
- rad_gruchalski 3y ago„So let’s give them an API to make their job easier!”
- panarky 3y agoMaybe information that's not secret or confidential, but could still be used to exploit you, should be called something like "sensitive" information.
- dexwiz 3y agoThere are levels of data classification, and different regulations and policies apply to each level and geo. They are probably disavowing themselves of any liability. https://docs.aws.amazon.com/whitepapers/latest/data-classification/data-classification-models-and-schemes.html https://docs.aws.amazon.com/whitepapers/latest/data-classifi...
- raid2000 3y agoThis is a good question for any provider like AWS--what kinds of information do I leak with seemlingly mundane choices like bucket names. The other attack vector is from insiders. Many organizations "shield" identifiable information behind UUIDs or some other scheme. In the event of a breach, the UUID might mean nothing to most (it's not foolproof, though), but opens more doors for an insider.
- deleted 3y ago[deleted]
- chrisjj 3y ago> they are not considered secret, sensitive, or confidential information ... by us (it should say). Users may consider it differently.