Mapping out the cloud!
This section is important—in fact, it might be the most important takeaway from this part of the book.
The full power of a knowledge graph can be understood when we start mapping out data outside of our immediate network. Remember that earlier in the book we discussed how red teaming should focus on exploring the unknown and provide alternate analysis. Often, graphs are being built that stop within corporate on-premises boundaries. This is not where you should stop, though! This is because the graph is missing key assets that modern organizations leverage. In many cases, the most important assets are not on premises anymore. Consider cloud assets, such as AWS, Azure, Salesforce, Facebook, Twitter, and so on.
All of these are commonly targeted by adversaries. For instance, consider Twitter or Facebook account takeovers. There have been a large number of high-profile incidents in these regards, and they are often not even on the radar for red teams...
