You're reading from API Security for White Hat Hackers Uncover offensive defense strategies and get up to speed with secure API implementation

Product type Paperback

Published in Jun 2024

Publisher Packt

ISBN-13 9781800560802

Length 418 pages

Edition 1st Edition

Concepts

Ethical Hacking

Author (1):

Confidence Staveley

View More author details

Table of Contents (20) Chapters

Preface

1. Part 1: Understanding API Security Fundamentals FREE CHAPTER

2. Chapter 1: Introduction to API Architecture and Security

3. Chapter 2: The Evolving API Threat Landscape and Security Considerations

4. Chapter 3: OWASP API Security Top 10 Explained

5. Part 2: Offensive API Hacking

6. Chapter 4: API Attack Strategies and Tactics

7. Chapter 5: Exploiting API Vulnerabilities

8. Chapter 6: Bypassing API Authentication and Authorization Controls

9. Chapter 7: Attacking API Input Validation and Encryption Techniques

10. Part 3: Advanced Techniques for API Security Testing and Exploitation

11. Chapter 8: API Vulnerability Assessment and Penetration Testing

12. Chapter 9: Advanced API Testing: Approaches, Tools, and Frameworks

13. Chapter 10: Using Evasion Techniques

14. Part 4: API Security for Technical Management Professionals

15. Chapter 11: Best Practices for Secure API Design and Implementation

16. Chapter 12: Challenges and Considerations for API Security in Large Enterprises

17. Chapter 13: Implementing Effective API Governance and Risk Management Initiatives

18. Index

Why subscribe?

19. Other Books You May Enjoy

Bypassing role-based and attribute-based access controls

Role-based access control (RBAC) and attribute-based access control (ABAC) are two popular approaches to data security in organizations. RBAC focuses on managing access based on an individual’s role within the organization, allowing them to access data relevant to their job functions. RBAC typically controls access to tables, columns, and cells, and is often implemented through table access control lists (ACLs). However, RBAC may not be suitable for organization-wide implementation as it is more consumer-specific.

On the other hand, ABAC is an approach that grants or restricts data access based on assigned attributes related to users, objects, actions, and the environment. ABAC offers a more dynamic and flexible model compared to RBAC. It allows for the independent provisioning of policies, users, and objects, and access control decisions are made at the time of data request based on the specified attributes.

Both...