People | Local Reqs | Source Code | Integration | Deployment | Runtime | Hardware | DNS | Services | Cloud |
---|---|---|---|---|---|---|---|---|---|
Developers | IDE | Languages | SCM providers | Build solutions | Servers | Embedded PC | URL | SaaS solutions | CDN |
QA team | SCV | Frameworks | Pull requests | Deployment platforms | Operating systems | PCB | hostname | Third party APIs | Cloud services |
DevOps team | Local tests | Libraries | Secrets mgmt | Unit tests | Webservers | USB dongle | Payment gateways | ||
Git repos | Package Managers | Functional tests | Application servers | GPU/CPU | Identity Providers | ||||
Proprietary code | Security tests | Web engines | Analytics | ||||||
Open source | API test frameworks | Databases | |||||||
People | Local Reqs | Source Code | Integration | Deployment | Runtime | Hardware | DNS | Services | Cloud |
This refers to the process of identifying and describing the external services that a application relies on in order to function properly. These third-party services can include anything from authentication and authorization services to payment processing and analytics tools.
- third party SaaS solutions
- third party APIs or data
- payment processors/gateways
- identity providers
- analytics & tracking
- CloudOps team
- Marketing team
- Centralized audit logs
- Vendor key management
- Content security policy
- Just in time access control