playbook_viewer | visualize threats without having attribution to a specific

playbook_viewer is a CSS library. playbook_viewer has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

over the past few years, we’ve been tossing around the idea of an “adversary playbook.” the idea is rather straightforward: just as we create offensive and defensive playbooks for sports, our adversaries also have offensive playbooks that they execute to compromise organizations. they may not write them down, but they exist. through observation and data sharing, defenders can create their own version of the adversary's playbook, and then use that playbook to better defend their network with defensive playbooks. the goal of the playbook is to organize the tools, techniques, and procedures that an adversary uses into a structured format, which can be shared with others, and built upon. to achieve this goal, we didn’t want to develop a proprietary structure that would be exclusive to palo alto networks. instead, we identified two frameworks that would enable us to not only structure our data, but also enable us to share it with others. stix 2.0 is the latest iteration of the stix format. it has been re-designed to simplify the creation of documents and uses json rather than xml. stix 2.0 provides a list of objects to represent types of information typically generated for cyber threat intelligence (cti). for instance, stix includes objects for intrusion sets, malware, and indicators, among