Reference
- 38 resources
- 5 links
- 2 sites (1 cloud, 1 on-prem)
- 2 systems
- 3 apps
- 2 databases
- 4 servers
- 1 saas
Views
Application flows
Every flow between the apps, databases and SaaS, as written in the registry.
Network
The servers by site and subnet, with the application flows lifted onto the machines that host them.
Subnets
The flows between subnets, merged by port: what the firewall rules must allow.
Landscape
The flows between the systems and the SaaS, in the direction of the data.
To verify
The resources and flows assumed or doubtful, or with an open question: what remains to confirm.
Ownership
The apps, databases and SaaS by owner team, with their operator.
To complete
The resources missing something for a complete model.
Between the sites
The flows and the connectors between the sites, with the SaaS reached from them.
Personal data
The flows carrying personal data, in red: where the customer details travel.
Customer trail
The customer details followed step by step from the CRM database.
Firewall matrix
The flows through the datacenter firewall, merged by port: its rule table.
Security
The servers and firewalls by site and subnet, every flow split at the devices it traverses.
Physical
The servers, switches and firewalls by site and rack, with their cabling.
Deployment
What runs where: the apps and databases with the servers hosting them.
Egress
The flows to the SaaS and the devices they leave through, deduced from the egress of the VPC.
If fw01 fails
What becomes unavailable when the datacenter firewall fails: the impact analysis.
If both web servers fail
web01 and web02 down together: in red, the apps and data that become unavailable.
Monthly invoicing
The monthly invoicing process, its links numbered as its steps, and its sequence diagram.
Systems
- invoicing Invoicing and customer relationship
- accounting