1. Simple addition of a printer to a network
    1. End user / Staff member acquires off the shelf printer from retail establishment
    2. End user is able to plug the printer into the network simply, and provide print services for all staff in the office space
    3. Engagement of IT staff should not be necessary
  2. Provisioning of services (2 servers/services)
    1. SERVER 1 – Front end (ie. web server)
    2. SERVER 2 – Application (ie. oauth 2.x)
      • Services can be allocated as virtual servers or physical servers
      • Services should be allocated to correct security posture
        • WebServer should be provisioned as publicly available service
          • Implicit provisioning: Firewalling, access control lists, appropriate services visible (TCP 443)
          • Implicit provisioning: Ability to add scaling (multiple servers) via AWS ELB, or data center based ADC
        • App Server (authentication) should not be publicly available
          • Implicit provisioning: Services should be shielded by Firewalling / access control lists
          • Implicit provisioning: Services should be provided to the web tier (accessed by a single server, or scaled ELB/ADC farm)
          • Implicit provisioning:¬†Services should be made available to future offerings (ie. ¬†storage, database, services, content), with simple linking of SDN provisioning
          • Implicit provisioning: Ability to add scaling (multiple servers) via AWS ELB, or datacenter based ADC
      • VLAN segmentation / IP Subnets / Security Posture should be automated with SDN services
        • Some technologies / vendors will eliminate concepts like VLAN
        • The important concepts are:
          • Security postures
          • Ability to scale horizontally (utilization can trigger a scale event)
          • Ability to copy “provisioning / application build” to similar redundancy zones
            • could be an alternate data center
            • could be an alternate availability zone on AWS
          • This publicly provisioned service can be utilized as a front end, enabling subscription to additional services:
            • Databases
            • Storage
            • Services
            • Content