Scenario B: Internet Bank
Figure 1: Technical Architecture
The overall process of creating this organization will have three phases:
· Business architecture driven.
· Application architecture driven.
· Technical architecture driven.
Initial steps for bank business architecture
· Adopt a lightweight business architecture framework required to design it.
· Understand the strategy of the bank.
· Develop a business capability model for the bank.
· Identify and map essential banking value streams.
· Generate a bank-wide capability to the system matrix.
· Align bank transformation needs to capability clusters.
· Translate the capabilities changes required to a roadmap
· Web browser: Risks on the web browser include system damage, crash, lack of privacy, and misuse of private information (Pagano, 2012).
· Firewall: In this case, there may be improper administration, system compromise, or misconfiguration.
· Web server: The presence of unnecessary services, system failure, misconfiguration, lack of firewall protection.
· Database: Loss of data through tampering and design.
· Datacenter: Access and physical security or disasters.
Security component mode for internet bank required by the organization
Pagano, J. (2012, May). Microsoft Industry Reference Architecture. Retrieved from https://news.microsoft.com/download/presskits/msfinancial/docs/MIRAB.pdf
Interned Banking Database
Internet banking app