Security Conceptual Design Deliverable Template
From MIKE2.0 Methodology
-> You are here: Security Conceptual Design Deliverable Template
The Security Architecture is sometimes broken into a separate deliverable, depending on the complexity of the requirements. Some issues to consider in defining the security model are:
Security requirements will be particularly complex if the solution must service external clients or if the data is of a secretive nature. Security Standards should drive the Security Architecture.
Example 1 - Security Conceptual Design for an Inventory investment model
Listed below are example Security Conceptual Design for an Inventory investment model:
Security Conceptual Design
1. The following section (Security Conceptual Design) provides a high-level overview to Client solution elements and standards that System 2-0 adheres to.
2. Access to the Client system is controlled via XYZ managed web based applications.
3. Users typically interact with the BI client applications (i.e. Cognos or Business Objects) via their web browser.
4. Enabling a Secure FTP connection between the user and Client requires the existence of a fixed IP-address.
5. Users are unable to access or trigger applications hosted on any Client servers other then LPAR3. The specifically prevents users from controlling the ETL jobs used to move data between the ASDF Replica, BDS2, ODS2 or RDS database schemas.
Cognos users will require their own LDAP group to access SYSTEM reporting functionality.
Wiki asset search