In a course, this book was used as teaching material in a class for computer security. The read, reminded me of speaking software to a hardware engineer. Since the hardware engineer is coming from another level, the experience was like talking DOWN to the reader. The author seemed to want to "imp
Designing security architecture solutions
β Scribed by Ramachandran, Jay
- Publisher
- John Wiley
- Year
- 2002
- Tongue
- English
- Leaves
- 483
- Category
- Library
No coin nor oath required. For personal study only.
β¦ Table of Contents
Preface. Acknowledgments. PART I: ARCHITECTURE AND SECURITY. Chapter 1. Architecture Reviews. Chapter 2. Security Assessments. Chapter 3. Security Architecture Basics. Chapter 4. Architecture Patterns in Security. PART II: LOW-LEVEL ARCHITECTURE. Chapter 5. Code Review. Chapter 6. Cryptography. Chapter 7. Trusted Code. Chapter 8. Secure Communications. PART III: MID-LEVEL ARCHITECTURE. Chapter 9. Middleware Security. Chapter 10. Web Security. Chapter 11. Application and OS Security. Chapter 12. Database Security. PART IV: HIGH-LEVEL ARCHITECTURE. Chapter 13. Security Components. Chapter 14. Security and Other Architectural Goals. Chapter 15. Enterprise Security Architecture. PART V: BUSINESS CASES AND SECURITY. Chapter 16. Building Business Cases for Security. Conclusion. Glossary. Bibliography. Index.
β¦ Subjects
Computer security;IT-sΓ€kerhet;IT-saΜkerhet
π SIMILAR VOLUMES
There is an invisible elephant in this book: your application. And, it sits at the center of every topic we touch in each chapter we present. This book is for systems architects who are interested in building security into their applications. The book is designed to be useful to architects in three
<div><p>Security is usually an afterthought when organizations design microservices for cloud systems. Most companies today are exposed to potential security threats, but their responses are often more reactive than proactive. This leads to unnecessarily complicated systems that are hard to implemen
<div><p>Security is usually an afterthought when organizations design microservices for cloud systems. Most companies today are exposed to potential security threats, but their responses are often more reactive than proactive. This leads to unnecessarily complicated systems that are hard to implemen
<div><p>Security is usually an afterthought when organizations design microservices for cloud systems. Most companies today are exposed to potential security threats, but their responses are often more reactive than proactive. This leads to unnecessarily complicated systems that are hard to implemen
Security is usually an afterthought when organizations design microservices for cloud systems. Most companies today are exposed to potential security threats, but their responses are often more reactive than proactive. This leads to unnecessarily complicated systems that are hard to implement and ev