API Security
Everything You Need to Know to Protect Your APIs
Mar 17, 2021
Visibility • Protection • Resolution
Doc ver: 2021-03-04-01
Aaron Lieberman
Big Compass
Cloud Practice Manager and Architect
Dan Gordon
Traceable AI
Dir, Technical Evangelism
https://traceable.ai
1. API landscape
2. Microservices role in API security
3. The difficult task of protecting APIs
4. How visibility relates to API security
5. Business roles
6. Layered API security
7. Traceable Defense AI
8. Q&A
Agenda
Based on Aaron’s new e-book
The Practical Guide to API Security:
● MuleSoft, AWS, Confluent, Salesforce, and
Boomi partners
● Consulting - specializing in integrations,
related technologies, API development, and
API security
● We build connections between systems,
applications, people, and ideas
Introductions
● Cloud Practice Manager and
Architect at Big Compass
● API security practitioner
● API enthusiast, developer,
designer, and owner
● Denver MuleSoft Meetup Leader
and Presenter
● All Things Integration Meetup
Leader and Presenter
● Speaker, blogger, writer
Aaron Lieberman
Polling Question #1
API Landscape
API Growth
https://blog.postman.com/api-growth-rate/
Current API Landscape
https://blog.postman.com/api-growth-rate/
Current API
Threats
Landscape
10 - 55 Attacks
Per Month
51 - 200 Attacks
Per Month
Experienced API
Security Incident
Last Year
56% 22% 91%
Cyber Attack Report
API Attacks
Affect
Everyone “50 million Facebook accounts breached by
access-token-harvesting attack”
“T-Mobile Alerts 2.3 Million
Customers of Data Breach Tied to
Leaky API”
“US Postal Service Exposes 60 Million Users
in API Snafu”
API Visibility
● Massive growth in APIs
● Organizations commonly deploy APIs without
documenting
● Inventory management of APIs is crucial
API Evolution
● An API inventory is crucial to protecting your APIs
● You can’t protect what you don’t know about!
● Inventory is the first step in protecting your APIs
API
Protection
Security Across
Microservices
Microservices
Landscape
2018 Cloud Microservices
Revenue
2023 Projected Cloud
Microservices Revenue
$683.2M $1,880M
Microservices Report 2
Microservices Growth Rate Per Year
27.4%
Microservices Report
Monolith vs. Microservices
Monolithic Architecture Microservices Architecture
Traceability
Is Key
● APIs are decoupled from orchestration and business logic
● More microservices mean greater need to track
communication across all distributed services to detect
abnormal behavior
● Not just monitoring 1 system, you are monitoring many
distributed microservices
The Difficult Task of
Protecting APIs
API Attack Detection Data
Average Cost of Data
Breach
Time to Identify and Contain
a Breach
Average Records Stolen in
Data Breach
$3.92M 279 days 25,575
● API breaches can take months or years to detect
● High volume of traffic across many APIs
● High velocity connections
● Diverse traffic running through many APIs
● API ownership is not always clear
● Advanced API attacks reduce effectiveness of
traditional API security measures
API Attack
Detection
Advanced
API Attacks
● OWASP API Top 10 identifies known attacks
● Hackers launch advanced attacks using ML/AI
● Advanced attacks are unpredictable
Polling Question #2
Business Roles
● Enterprise Architects
● API Developers
● Information Security
● Operations/Support
Business Roles
Necessary to Protect
APIs
Roles in API Security
Layered API Security
● Protects against brute force attacks and other
simple attacks
● Gateway security measures
○ OAuth 2.0
○ Rate limiting
○ IP whitelisting
○ Client ID enforcement
○ JWT
○ SAML
First Line of
Defense - API
Gateway
Security
● Protects against some of the OWASP Top 10 Attacks
● Entry point to API Gateway and backend services
and detects attacks such as
○ SQL injection
○ Cross site scripting
○ DDoS
Second Line of
Defense -
WAF/RASP
● Last line of defense that models the behavior of your
API
● Can detect deviations from normal behavior
● Protects against advanced attacks from
○ Stolen tokens
○ Insider threats
○ Stolen credentials
○ Authenticated access
Third Line of
Defense -
ML/AI
A New Approach to
Application & API Protection
Traceable Defense AI
Hypertrace
Distributed Tracing
Trace AI Platform
Unsupervised Machine Learning
Defense AI
30
Real-time complete
service, API, & data
visibility
Visibility
(WAF+RASP+API)++
AI first, no rules
required, low false
positives
Protection
Per transaction
contextual data for
Dev, Sec, and Ops
Resolution
31
● Complete
visualization of
your apps
● Understands
interactions between
your services
● Understands flow of
traffic between
services
● Understands who’s
using your services
● Understands data
flow between
services
Visibility - Complete app security discovery & observability
Visibility - Real-time API Discovery & Risk Scoring
32
● Discovers
external and
internal API
usage in
real-time
● Continuous API
endpoint risk
scoring based
on API
Intelligence
● Understands &
models API
behavior
● No more shadow
API’s
Protection - AI First Detection, No Rules Required
● Beyond WAFs & RASPS
- no rules required,
low false positives
● Protects against
OWASP & OWASP API
top 10 threat lists
● User focused threat
activity timelines
● Evolve defenses to
match continuously
changing threats and
application
architectures
33
34
● Understands user
behavior
● Detects & blocks
anomalous user
behavior
● Prevents fraud
attacks
● Stops data
breaches
Protection - Block sophisticated business logic attacks
35
● Per transaction
explorable data lake
for forensics and
troubleshooting
● Increase resolution
velocity due to
shared visibility
● Closely align SecOps
and Dev teams
● Help developers to
understand API
security risks
Resolution - Contextual Data for Dev, Sec and Ops
https://traceable.ai
Q&A
Visit us to learn more:
Visibility • Protection • Resolution
https://www.bigcompass.com
Appendix
Helpful Links
and
References
● IBM Breach Data Report
● Data Breach Statistics
● API Attack Statistics
● Big Compass eBooks

API Security - Everything You Need to Know To Protect Your APIs

  • 1.
    API Security Everything YouNeed to Know to Protect Your APIs Mar 17, 2021 Visibility • Protection • Resolution Doc ver: 2021-03-04-01 Aaron Lieberman Big Compass Cloud Practice Manager and Architect Dan Gordon Traceable AI Dir, Technical Evangelism
  • 2.
    https://traceable.ai 1. API landscape 2.Microservices role in API security 3. The difficult task of protecting APIs 4. How visibility relates to API security 5. Business roles 6. Layered API security 7. Traceable Defense AI 8. Q&A Agenda Based on Aaron’s new e-book The Practical Guide to API Security:
  • 3.
    ● MuleSoft, AWS,Confluent, Salesforce, and Boomi partners ● Consulting - specializing in integrations, related technologies, API development, and API security ● We build connections between systems, applications, people, and ideas Introductions ● Cloud Practice Manager and Architect at Big Compass ● API security practitioner ● API enthusiast, developer, designer, and owner ● Denver MuleSoft Meetup Leader and Presenter ● All Things Integration Meetup Leader and Presenter ● Speaker, blogger, writer Aaron Lieberman
  • 4.
  • 5.
  • 6.
  • 7.
  • 8.
    Current API Threats Landscape 10 -55 Attacks Per Month 51 - 200 Attacks Per Month Experienced API Security Incident Last Year 56% 22% 91% Cyber Attack Report
  • 9.
    API Attacks Affect Everyone “50million Facebook accounts breached by access-token-harvesting attack” “T-Mobile Alerts 2.3 Million Customers of Data Breach Tied to Leaky API” “US Postal Service Exposes 60 Million Users in API Snafu”
  • 10.
  • 11.
    ● Massive growthin APIs ● Organizations commonly deploy APIs without documenting ● Inventory management of APIs is crucial API Evolution
  • 12.
    ● An APIinventory is crucial to protecting your APIs ● You can’t protect what you don’t know about! ● Inventory is the first step in protecting your APIs API Protection
  • 13.
  • 14.
    Microservices Landscape 2018 Cloud Microservices Revenue 2023Projected Cloud Microservices Revenue $683.2M $1,880M Microservices Report 2 Microservices Growth Rate Per Year 27.4% Microservices Report
  • 15.
    Monolith vs. Microservices MonolithicArchitecture Microservices Architecture
  • 16.
    Traceability Is Key ● APIsare decoupled from orchestration and business logic ● More microservices mean greater need to track communication across all distributed services to detect abnormal behavior ● Not just monitoring 1 system, you are monitoring many distributed microservices
  • 17.
    The Difficult Taskof Protecting APIs
  • 18.
    API Attack DetectionData Average Cost of Data Breach Time to Identify and Contain a Breach Average Records Stolen in Data Breach $3.92M 279 days 25,575
  • 19.
    ● API breachescan take months or years to detect ● High volume of traffic across many APIs ● High velocity connections ● Diverse traffic running through many APIs ● API ownership is not always clear ● Advanced API attacks reduce effectiveness of traditional API security measures API Attack Detection
  • 20.
    Advanced API Attacks ● OWASPAPI Top 10 identifies known attacks ● Hackers launch advanced attacks using ML/AI ● Advanced attacks are unpredictable
  • 21.
  • 22.
  • 23.
    ● Enterprise Architects ●API Developers ● Information Security ● Operations/Support Business Roles Necessary to Protect APIs
  • 24.
    Roles in APISecurity
  • 25.
  • 26.
    ● Protects againstbrute force attacks and other simple attacks ● Gateway security measures ○ OAuth 2.0 ○ Rate limiting ○ IP whitelisting ○ Client ID enforcement ○ JWT ○ SAML First Line of Defense - API Gateway Security
  • 27.
    ● Protects againstsome of the OWASP Top 10 Attacks ● Entry point to API Gateway and backend services and detects attacks such as ○ SQL injection ○ Cross site scripting ○ DDoS Second Line of Defense - WAF/RASP
  • 28.
    ● Last lineof defense that models the behavior of your API ● Can detect deviations from normal behavior ● Protects against advanced attacks from ○ Stolen tokens ○ Insider threats ○ Stolen credentials ○ Authenticated access Third Line of Defense - ML/AI
  • 29.
    A New Approachto Application & API Protection
  • 30.
    Traceable Defense AI Hypertrace DistributedTracing Trace AI Platform Unsupervised Machine Learning Defense AI 30 Real-time complete service, API, & data visibility Visibility (WAF+RASP+API)++ AI first, no rules required, low false positives Protection Per transaction contextual data for Dev, Sec, and Ops Resolution
  • 31.
    31 ● Complete visualization of yourapps ● Understands interactions between your services ● Understands flow of traffic between services ● Understands who’s using your services ● Understands data flow between services Visibility - Complete app security discovery & observability
  • 32.
    Visibility - Real-timeAPI Discovery & Risk Scoring 32 ● Discovers external and internal API usage in real-time ● Continuous API endpoint risk scoring based on API Intelligence ● Understands & models API behavior ● No more shadow API’s
  • 33.
    Protection - AIFirst Detection, No Rules Required ● Beyond WAFs & RASPS - no rules required, low false positives ● Protects against OWASP & OWASP API top 10 threat lists ● User focused threat activity timelines ● Evolve defenses to match continuously changing threats and application architectures 33
  • 34.
    34 ● Understands user behavior ●Detects & blocks anomalous user behavior ● Prevents fraud attacks ● Stops data breaches Protection - Block sophisticated business logic attacks
  • 35.
    35 ● Per transaction explorabledata lake for forensics and troubleshooting ● Increase resolution velocity due to shared visibility ● Closely align SecOps and Dev teams ● Help developers to understand API security risks Resolution - Contextual Data for Dev, Sec and Ops
  • 36.
    https://traceable.ai Q&A Visit us tolearn more: Visibility • Protection • Resolution https://www.bigcompass.com
  • 37.
  • 38.
    Helpful Links and References ● IBMBreach Data Report ● Data Breach Statistics ● API Attack Statistics ● Big Compass eBooks