Across
- 6. SABSA builder’s view for translating logical designs into physical implementations.
- 7. Framework that aligns enterprise architecture practices with security requirements.
- 8. SABSA lifecycle phase for developing detailed security architectures.
- 11. Policies, procedures, and technologies used to protect against identified risks.
- 13. Framework that enhances governance and management of IT processes.
- 17. Lifecycle phase that defines security direction and aligns it with business objectives.
- 18. SABSA principle requiring security strategies to support business objectives.
- 21. Access-control model that assigns permissions to roles and roles to users.
- 22. Framework that supports effective management of IT services and operations.
- 23. Active interactions in which users exercise assigned roles.
Down
- 1. Protection of data, systems, and networks from threats and vulnerabilities.
- 2. Intermediate component placed between a client and a server.
- 3. System that requests services or authorization from a server.
- 4. Continuous observation used to detect breaches, anomalies, and security incidents.
- 5. Access-control model in which the owner of a resource determines access.
- 7. Confidence that privileges will be exercised appropriately.
- 9. OM-AM layer that articulates security objectives and trade-offs.
- 10. SABSA designer’s view for designing security components and their interactions.
- 12. Sherwood Applied Business Security Architecture framework.
- 14. Comprehensive framework for ensuring the security of an organization’s IT infrastructure.
- 15. Access-control model based on mandatory system rules and security labels.
- 16. Rules that define the acceptable use and protection of information assets.
- 19. System that provides services and may obtain authorization information.
- 20. Job-based groups used to assign permissions to users.
- 21. Potential threats that could affect organizational assets and operations.
