Running head: SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT Systems Integration OS Banking Security Project (IIII) ITSD425 Unit4 First Last School 1 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT2 1. Project Information 3 2. Project Plan 4 3. System Integration Best Practices 5 Project Plan 9 4. Requirements Specifications 13 5. Enterprise System Integration Analysis 21 6. Systems Integration Approach Evaluation and Selection 25 7. Proposed System Integration Components Architecture 30 8. Implementation Framework 33 9. System Integration Implementation Plan 35 References 36 2 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT3 1. Project Information Operating system Security (OS security) is a data and information protection integrated system that aims at ensuring the availability, integrity, and confidentiality of data. In the modern day, information technology has skyrocketed leading to new and viable information security systems. However, with a similar rate, cybercrime and other forms of data confidentiality breach and identity thefts have thrived (Cameron et al. 2010). Criminals use such websites as Dark web and sophisticated software to infiltrate information system and cause information and data vulnerability. OS integrated security system comes to the rescue of individuals and organizations in protecting the OS from hacker intrusions, malware, viruses, worms, and other forms of threats. The OS security is an integration of all preventive control techniques used in ensuring data safety. For example, single physical computing hardware that shares I/O devices, disk, and CPU among others tend to be vulnerable to threats and attacks from multiple access points (In Vacca, 2014). The target of any hacker is to control the operating system where the key to all other access points lies. The bank is one enterprise that is targeted by hackers either directly to its servers or via the security details of the customers. Hackers try to infiltrate the servers and Central Processing Unit of a banking organization, so that they can introduce malware that can help them take control of the banking system and credit their accounts with money (Cameron et al. 2010). On the other hand, they also hack the customer’s security systems and steal their identity and in the process withdrawing all their money (Tran & Park, 2014). 3 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT4 2. Project Plan The aim of the project is to employ OS integrated security system in safeguarding data and information integrity and protection. Security provision refers to the aspect of ensuring such computer systems as software programs, disks, CPU and the memory are all protected from malware, manipulation, threats, worms, viruses, and malicious and unauthorized access. The project aims at using an integrated OS security system to promote data and information integrity and security for the banking sector. The upgrading of the organization’s data security system will be the priority of the project by ensuring that the OS security systems are integrated in such a manner that data integrity and security for the banking sector is enhanced. Some of the vulnerabilities that lead to security breach include the user’s use of weak passwords. Secondly, poor data encryption system, such programs threats as Trojan horse, virus, logic bomb, and Trapdoor. The organization’s system is prone to such threats as worm, port scanning, and denial of service (Silberschatz, Gagne & Galvin, 2013). 4 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT5 3. System Integration Best Practices In a bid to enhance the OS security system integration, some desirable practices should be practiced by every bank staff and stakeholders. The operating system can be secured through best practices that mitigate the vulnerability of the entire information security system. When it comes to the user accounts in the bank, the number if computers connected to the organization’s server must be limited. Only a few trusted users should be allowed to access the bank's server via computers as this would give ease in maintaining accountability (Silberschatz, Gagne & Galvin, 2013). When it comes to account policies, strong password for both personal computers (PCs) and the server should be made as string as possible with frequent password change schedule. The file system should be designed in such a manner that it grants read-only access permissions to discourage the hackers. The system should be set to deny access by default if it identifies unauthorized access (Tran & Park, 2014). When it comes to the bank’s network services, the level of access permissions by the users should be limited and restrictive to the public. Most importantly, the latest vendor patches for the OS security must be functional and integrated into the entire system. Also, a regular maintenance schedule should be set for an update of security patches (Tran & Park, 2014). Considering that the bank has multiple operations, there is need to implement a protection for buffer overflow using third party software. System login files must be monitored frequently while ensuring that they are safe by restricting access permissions to them. Finally, the system resources should be backed up on a regular basis (In Vacca, 2014). Enterprise Information 5 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT6 The banking sector is one of the areas that high-level sensitivity information is stored. There is thus the need to boost information security measures to mitigate the vulnerabilities that have been causing multiple cyber-attacks on banks. Many banks have lost money through direct infiltration in their databases or through external attacks whereby client’s identity is stolen and used to access their accounts (In Vacca, 2014). Valley wood Bank is one institution that has reported four major cyber-attacks that have cost its running and public confidence a great deal. Security measures have been upgraded after every attack but the attackers have always found new strategies to conquer the banks data protection system. As a result, there is need to see to it that the bank adopts a new security system that is reliable and effective in ensuring data security (Silberschatz, Gagne & Galvin, 2013). Project Objectives The objectives of the project are to restore public confidence in trusting the bank again with their money by coming up with a long terms solution to data and information security for both the bank’s database and the user’s schema. The project will, therefore, look to fulfilling the following objectives; ● Outlining and demonstrating the importance of OS security system in a banking system ● Make an enterprise system integration analysis on Valley Wood Bank ● Evaluate how the application of OS security can ensure data security and confidentiality for the bank are enhanced ● Analysing strategies to protect the bank from current and future threats The planning of an effective OS security system that can be adopted by Valley wood bank to ensure a long-term security system (Silberschatz, Gagne & Galvin, 2013). 6 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT7 Business/Technical Needs to be met by the Project Considering the sensitivity of the information that pertains to financial matters for clients on their savings, the project should meet number if technical aspects. First, many customers are resulting to online backing and other major financial transactions that link to the bank. There is thus the need to ensure that the customer is protected while they use the mobile banking that has become the new trend in the banking industry (In Vacca, 2014). Valley wood should stop using weak and old system security measures and adopt the OS security system. The OS of any system tends to control major operations of the entire organization. As a result, protecting the customer and organization by first boosting the security of the OS is recommendable. The first technical aspect will be to upgrade and implement better and secure communication methods within the bank and with the clients. Communication system that is insecure is detrimental for any organization considering that information is the greatest weapon an organization can have. Internal and external banking communication will be addressed. Secondly, the need to create a strong password strategy for the bank and the user’s systems will be crucial (Silberschatz, Gagne & Galvin, 2013). The project will also advocate for the creation of internal awareness to threats in the bank by ensuring that internal protocols are strengthened. Creation of awareness on both employees and customers will be a boost to the security system of the bank. Most importantly, the project looks at formulating a plan to strengthen database security by integrating a safe OS security system to control internal security aspects (In Vacca, 2014). Moreover, it will outline the creation of a secure backup plan by analysing data centre management and application of cloud computing to the Os security system to enable addressing security concerns for customers (Silberschatz, Gagne & Galvin, 2013). An 7 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT8 upgraded security system that will utilize OS security system to enhance security by sending alarm signals to alert the customer or the bank on any probable attempts to access the user’s account or the bank’s database. Other technical improvements will include better authentication processes. It will also outline improved authorization processes controlled by the banks database. The other aspect is resource protection by setting up a system that gives limited access to vital areas in the organization. Data and system integrity will be enhanced as well. In addition, other aspects to be addressed will include nonrepudiation and confidentiality. Major Components to be integrated In a bid to enhance a reliable OS security system, many major components will be integrated to make up a complete system. The first component will be the server and the second will be the database. These are the core components that are regulated by the operating system and if infiltrated or compromised, they lead to outright cyber-attacks or corruption of data by malware. Other components will involve a video surveillance system with IP cameras being installed. Intruder alarms will also be integrated in the system and linked to the IP cameras to enhance the video surveillance. Access control forms the other OS security integrated component each subsystem will be expected to have an access control system so that any suspicious access attempt can be recorded and relayed to the alarm system and to the server. Alarms and visitor management platforms will form part of the access control. Standards and protocol control system will also be a part of the OS security integration and they will give access protocols that discourage identity theft and infiltration (In Vacca, 2014). 8 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT9 Centralized control will also be a must have integration linked directly to the OS system. Customers will be able to view all security aspects using a single user interface. With the availability of a centralized control integrated to a video surveillance, and access control, greater visibility and control will be enhanced. The OS security system will utilize this integration in delivering secure and reliable integrity information. Boundaries of the Project (what it will not address) The project will not consider the actual software development for OS security system but it will assume that the software is already there. It will only major on its design, planning and implementation to show how banking security can be improved. It will also not address the various types of system vulnerabilities, malware and viruses among other aspects that lead to cyber insecurity. It will just mention them briefly. Project Plan Work Breakdown Structure In a bid to ensure that the scope and objectives of the project are achieved with minimal wastage of human resource and in ensuring timely delivery of the project, a Work Breakdown Structure is important. Task Scope definition Project objectives Threat analysis Streamlining communication System security Requirement specification Software requirements Authentication Start Date End Date Task Bearer 6/11/2017 9/11/2017 12/11/2017 8/11/2017 10/11/2017 14/11/2017 John Lucy Cleopas 15/11/2017 18/11/2017 James 19/11/2017 20/11/2017 Billy 21/11/2017 23/11/2017 Zack 9 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT10 requirements Security Monitoring and control Design Systems Integration Approach 24/11/2017 27/11/2017 26/11/2017 28/11/2017 Lucy John 29/11/2017 1/12/2017 Billy Integration Components 2/12/2017 4/12/2017 James Technical needs 5/12/2017 6/12/2017 Billy 8/12/2017 10/12/2017 Cleoppas Lucy 15/12/2017 17/12/2017 Zack Implementation Implementation Frameworks System integration implementation plan Process Flow Diagram OS Security System Development Project Definition and Design scope Implement ation Project Objectives Systems Threat analysis Integration Approach Integration Streamline Components Technical communication needs System security System integration implementation plan Software requirements hardware 10 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT11 Requirement specification Control and authentication monitoring List of Resources required completing Project The project will require IT and system installation expertise. Hardware infrastructure such as alarm systems, surveillance videos, servers, database, LAN and WAN integration components, and computer subsystems will be part of the required resources. When it comes to software requirements, cloud computing programs, and signal sensors to be integrated to the customer’s phone. Installation capital will also be needed to see the project to completion (Silberschatz, Gagne & Galvin, 2013). 11 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT12 4. Requirements Specifications For the upgrading and installation of an effective OS security to be effective, there is need to analyse software requirement specification for the project. It is the determination of what the OS security will do and its expectations to perform. Software Requirement Specification (SRS) will be used as vision tool since the security of banking security has been a global concern (In Oshana & In Kraeling, 2013). In this case, the banking OS Security system will require some performance and software requirements so that it can work effectively in protecting customer information, and possibilities of hacking. First, the OS security system will have to route the bank’s defined internal communication systems and route them to external networks. This is a requirement that will need authentication proxy servers to be installed. The servers will be managed boundary protected interfaces. The proxy server will be designed in such a way that it hides the identity of the clients whenever they decide to make connections to the server on the outside of the bank’s networks. As a result, any hacking attempt outside of the learning IP will be prevented (Jacobs, 2014). The other requirement will be the need to ensure that the OS security system communicates outside the communication path of the bank to prevent remote devices that can establish a non-remote connection from hacking into the bank's main server. The project will consider authentication, communication, software, hardware, and intrusion monitoring requirements needed to ensure that the OS security of the bank will be implemented effectively (In Oshana & In Kraeling, 2013). Authentication Requirements These refer to the strategies that the OS security system will employ in resolving such issues as expiry of inactive sessions, forgotten passwords, and account lockouts among other 12 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT13 customer-related challenges that pose vulnerability to the bank. The system will need to determine whether someone is whom they claim to be and decide that will either deny or allow them access (Yang & Alves-Foss, 2013). Communication Requirements In ensuring an effective communication system, such requirements as reliable internet system will be considered. The running of a banking system must be efficient enough to make online transactions as quickly as possible while ensuring data security is maintained. For the project to be completed effectively, a proper chain of communication will be determined so that all project requirements can be communicated effectively (Yang & AlvesFoss, 2013). The OS will, therefore, establish an internet connection that can assist the stakeholders to surf and make other online transactions. Requirements needed to make communication protocols between the bank and the client will be enabled by an effective OS security system that will ensure that no information communication platform is infiltrated. Therefore, requirements on the management of Wi-Fi and Ethernet connections will be considered so that seamless communication can occur between the bank and the client, or the client and the machine during a financial interaction (Yang & Alves-Foss, 2013). Software Requirements When it comes to software requirements, the OS security system will ensure that the software used is strong and efficient enough to protect the bank's database and its servers. The first thing will be to train clients and the banking staff on cybersecurity (Jacobs, 2014). The aspect of firewall protection to enable internet protection for customers will be considered. Thirdly, keeping the software up to date is an important aspect that ensures malicious attacks on the OS security system does not happen. Up--to-date browser will see to it that security is enhanced (Peltier, 2014). 13 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT14 Provision of antivirus for the banking software and the user machine devices is a crucial requirement. Anti-virus is meant to keep viruses that hackers put on the internet from infiltrating user and bank systems to create vulnerabilities that they can exploit (Yang & Alves-Foss, 2013). The anti-spyware software will be installed in the OS security system to ensure that malicious attempts are reported as early as the hacker tried to access the database and appropriate measures taken by the system on an automated response. Other aspects to be considered in the OS security software include efficiency and cost. The software used must be efficient enough to handle bulky transactions and security capabilities. This is because a bank is an outright target for cybercriminals and thus vigilance if required. Secondly, the complexity of infiltration capability will be considered to measure how strong the bank's security system will be (Serpanos & Wolf, 2011). When it comes to cost, the software must be of quality performance and fair price based on its durability and efficiency in protecting organizational data and transactions. 14 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT15 Hardware Requirements In hardware requirements, the project will look at enhancing security in hardware components that support the bank. First, it will look at enhancing security to its servers and database. Thirdly, external storage protection for hard disks and usage of external data storage devices will have to be regulated by both organizational staff and clients. The type of browsers that the bank will use will also be evaluated (Serpanos & Wolf, 2011). Intrusion and Monitoring Requirements Some of the intrusion and monitoring requirements needed for the project include database security. It will consider protecting the bank from the following threats; Trojan, worms, spyware, malware, security software that are rogue, phishing, spam, and rootkit among others (Yang & Alves-Foss, 2013). The bank's database and the way users use online transactions, and their vigilance to cybercrime will be the requirements for intrusion and data safety. Functional Requirements In the authentication requirements analysis, software as a service (SaaS) requirements will be considered for this project. The first one will be to ensure that the OS Security system provides security and control on any banking function based on authenticated permissions. Secondly, provision mechanism for the system will be made so that users with user data that tend to conduct their business in an on-environment can gain control in the on-demand environment (Serpanos & Wolf, 2011). Thirdly, user data will reside in a shared database in an on-demand environment but a different database schema. Therefore, the OS security system for the bank will see to it that a mechanism is set for authorization and authentication of clients against a shared database but ensure a specific schema in the same database for each client (In Oshana & In Kraeling, 2013). Strong password policies will also be required to ensure that clients do not use weak passwords to access their bank accounts. 15 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT16 Moreover, the bank will also be required to have strong passwords for its servers which will be changed regularly and in possession of only senior trustees. Password complexity is an organizational requirement that will see to it that special characters are used by both the bank officials and customers (Yang & Alves-Foss, 2013). The passwords will be required to have enough strength to counter the brute-force of hackers during infiltration. The aspects of authentication and authorization will be taken seriously. The project will, therefore, consider both user and machine authentication in its security requirements. User authentication will involve such considerations as thumbprints, strong passwords, and ID. When it comes to machine authorization, frequent updates and patching on the banking system will be considered while ensuring a strong machine authentication (Peltier, 2014). Non-Functional Requirements The use of OS security system will upgrade the reliability requirement. The ability to see to it that the banking system is free of frequent attacks on its database as well as vulnerability of customer’s information will be enabled. Another requirement will be the need for maintainability of the system (Hines & University of Waterloo, 2011). After the completion of the project, maintenance experts will be required to ensure that it is not infiltrated due to customer or staff ignorance, nor better capability of cyber criminals to infiltrate the system. Frequent service will also have to be done of the system to ensure that it is up to date with detection of vulnerabilities and alerting the management of a possible cyber-attack on the bank’s database. Data integrity will also be a priority of the project an aspect that will be enabled by a reliable management (Erder & Pureur, 2016). Other requirements to consider include ease in usability of the system by the customer as well as better data recoverability. Stakeholders and their Roles 16 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT17 The stakeholders for the project will include many experts who will handle various software developments and its installation in the bank. Their task will involve building, testing, and installation of the OS security system that will ensure that the risks and vulnerabilities of the system are mitigated. Each group of stakeholders will handle different roles and requirements needed to see the project complete and successful. The first set of stakeholders will be the production engineers who will be given the responsibility of designing and testing an effective OS security system which will be installed in the banking system. The work of production Engineers will generally be management of both software and hardware infrastructure that will be needed in the project (Erder & Pureur, 2016). They will also play the crucial role of installing the entire system and ensure that they test it to ensure it works well and has no loopholes. Secondly, the acquirers will see to it that the right components and requirements needed for the OS security development by the engineers is procured and delivered promptly. They will work closely with engineers to ensure that all requirements are delivered in time. In addition, the product will also engage the services of expert developers who may also be Engineers and they are expected to ensure that the system is developed in the right manner and deployed to the bank in question for installation (Robertson & Robertson, 2013). Working closely with acquirers, a reliable supplier will be identified and given the contract to deliver all the required software and hardware infrastructure. All the delivered items will strictly follow the project budget to avoid overspending that can lead to depletion of monetary resources. During and after the completion of the project, two assessors will be required to ensure that the developed OS security system conform to the standards and legal regulations of the government (Erder & Pureur, 2016). 17 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT18 System maintainers will be full time IT experts and bank employees and they will be tasked with managing the evolution of the OS security system by keeping vigilance on how it operates. This team of system maintainers will work closely with system administrators from the bank who will be running the system after its installation. The final stakeholder will be the user who will directly use the system to make their financial operation from the bank either in the bank or via the internet. Process of Eliciting Requirements An Agile approach was used to elicit for project security requirements for the bank. A research was first done on the best approach to mitigating cybercrime and information vulnerability in the banking sector. As a result, a stage for requirement solicitation was set after a clear understanding of the business value the project will fetch the bank. Some of the advantages included a higher customer rate of attraction due to secure and efficient banking system (Hines & University of Waterloo, 2011). The security requirements were identified in alignment to the bank’s goals and objectives. The second step was to define and confirm the scope of the project and the viability of applying an OS security system compared to other systems. The aspects involved in the scope and those out of it were stated clearly so that they could be applied in each stage of the software assessment, development, analysis and installation. The implementation of the scope was based on the objectives of the project which was to improve efficiency in data security and banking transactions (Robertson & Robertson, 2013). The third step was to understand the stakeholders and the optimal means that each was using to elicit the requirements. The aim was to see to it that each of the stakeholders agreed to the project’s requirements and was supportive enough. Therefore, prioritization of requirements was done in a continuous approach in each phase of the project. Finally, an 18 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT19 effective requirement analysis and development was done by the project engineers arranging them staring with the highest-priority requirement (Erder & Pureur, 2016). Component and Interfaces The banking OS security project will entail three convectional layers aimed at ensuring prompt delivery security solutions in the banking sector. It will use a conventional E-security system that requires pin and username. The second layer will entail biometric security which will involve an authentication requiring fingerprint or iris recognition. Finally, the last layer will be linked to the customer’s mobile phone. The OS security will be configured in such a manner that Mobile security will be enhanced using GPS technology with SMS alerts (Hines & University of Waterloo, 2011). The security system will handle both biometric and user data in the database. Security- Layer 1 Conventional E-Security (uses username and Pin) Bio metric Data Biometric Security User Data (Authentication via Iris recognition and Fingerprint) Layer 2 Mobile Security (GPS technology to send infiltration alerts to customer) 19 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT20 Security Layer 3 5. Enterprise System Integration Analysis The process of bringing together smaller components so that they can function as a single system is what is referred to as integration. In this case, the integration component that will be chosen will aim at stitching together different and disparate subsystems and consolidate them in a manner that they will work as a single system. This will enable quick sharing of data whenever needed as well as enhancing information security for banking transactions and other relevant customer information that may compromise the entire organization if not protected (Sherif, 2010). The adopted architecture will see to it that both the software and hardware systems are well incorporated to enhance communication and data security. In this project, the banking system will utilize OS security system in safeguarding of its information through integrated quality assurance. The use of quality assurance in the development and evaluation of the OS security system for the banking system will be to ensure that the set of procedure formulated in ensuring quality integrated operating system is enhanced (York & MacAlister, 2015). Quality control can be defined as the process of ensuring that a product which is manufactured adheres and aligns to the set of defined quality criteria (DelaHostria, 1997). It is a process of seeing to it that the requirements of the OS security system being designed are met and they satisfy the needs of the client, in this case, the bank. Quality Assurance (QA) and Quality control are two similar concepts but different in their objectives and implementation. When a product is still under development, the process of ensuring that it meets its requirements during the development process, is what can be defined as quality assurance. However, the two aspects work hand in hand and their main 20 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT21 objective is to see that both the requirements of the product under development and those of the client for whom the product is being developed, are met. In this case, the development of OS security integration system will consider three main integration approaches that will be considered potential for incorporation into the running of the newly designed OS security for the banking system. The design team will consider the employment of either Star integration system, vertical integration, or Horizontal integration also known as Enterprise Service Bus (ESB). An analysis of these potential integration components will be done to ascertain the most viable and compatible to the OS security system for the banking information security. Star Integration When it comes to the Star integration component also known as Spaghetti integration, the interconnection will take place in such a manner that each of the remaining security subsystems will be interconnected to various systems. The integration component got its name from the fact that it tends to form a STAR shaped integration web in its interconnections. However, upon complete interconnection of the subsystems, the formed shape forms a reminiscent of spaghetti (DelaHostria, 1997). In this case, the OS security subsystems will be exporting propriety interfaces and thus and this may lead to substantial rise in costs. The more the subsystems, the higher the cost of integration will rise. However, some of the main advantages that the Star integration component is expected to fetch the banking OS Security system in its flexibility in terms of reuse of its functionality. The interconnections will enable better information security through effective communication. Each department in the bank will be easier to manage using the spaghetti integration system (Sherif, 2010). Interdepartmental communication and its monitoring will be made better via the use of spaghetti integration as autonomous systems are tied together 21 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT22 by the development of point to point systems. The implementation of new application features tends to be faster due to lack of rigidity in the system thus depicting flexibility. Some of the disadvantages of Star integration include; the component is seen as a disorganized system as IT management team becomes disjointed. This may lead to problems in the long run. The other aspect involves cost, in case some change wants to be made on a single application or database, the presence of Star integration translates to a costly affair. The appearance of agility is created by the fact that changing a single system is faster, however, introduction of a new functionality leads to exponential rise in costs (York & MacAlister, 2015). The consolidation of Spaghetti integration to a single data-mart becomes difficult leading to poor decision making. Vertical Integration In vertical integration, the silos of functionality entities are created and they assist in the integration of subsystems based on their functionality. They are called vertical integration approaches because the interconnection of the functionalized subsystems is arranged in a vertical setting starting with the most basic function at the bottom and the rest piling up as their importance increases (Sherif, 2010). The main advantage of the process is that it is fast and would thus cost less in its initial integration as only few vendors will be involved. However, it becomes expensive with the formation of more silos so as to implement new functionalities. It, therefore, requires constant updating so that new functionalities can be integrated into the system. Horizontal Integration This is an integration process which will involve the creation of different interfaces in each subsystem. It means that new and unique subsystems have to be created when each integration is completed. This creates flexibility as the replacement of any interface in each 22 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT23 subsystem can be done with ease without interference with the other subsystems. The component of horizontal integration is also known as Enterprise Service Bus. Apparently Horizontal integration tends to be the most effective way for organizational expansion in terms of data security and information communication enhancement. The reason behind it is because it is cheap to buy (York & MacAlister, 2015). As companies grow, it becomes more lucrative making the cost of acquiring a new business much less. One advantage that this integration will fetch the banking sector is that since each subsystem has its own interface independent from the other system in terms of connectivity to the ESB, the cost of integration will be lowered and flexibility gained. It means that if one subsystem becomes vulnerable to malware or hacking and acts as loophole to the security of the entire OS system, then it can be replaced with another one which is secure. The role of the ESB will be to translate one interface to another without affecting the rest of the subsystems (Sherif, 2010). However, the cost of intermediate data transformation cannot be avoided and thus the system may be misleading. 6. Systems Integration Approach Evaluation and Selection The aspects that will be used to evaluate and compare the three integration components for OS security system integration will be competence, data integrity, and systematic inquiry efficiency (York & MacAlister, 2015). When it comes to competence, the ability of the integration systems to safeguard data and streamline internal communications by building efficiency will be determined. On the other hand, the aspect of integrity and honesty will involve the ability of the integration components to enhance impartiality, transparency, and independence of data safeguarding and communication (DelaHostria, 1997). 23 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT24 The system integration and evaluation of the Star, vertical and horizontal integration systems will involve determining which component is most ideal in allowing more control over the organization’s business. More control on information storage, security and communication will play a big role in the selection. Secondly, positive differentiation as a business strategy that will enable the bank to gain more information on changing data infiltration techniques and the best strategy to counter it. On the other hand, the component that has the lowest const transaction in the installation and maintenance of the integration system will be most viable. System maintenance can be costly for organizations and thus the more durable the integration system will be, the better. Quality Assurance Considerations Best Option to Proceed with in evaluating the three integration methods will largely depend on the American Evaluation Association. Its guiding principles will be used for evaluating the vertical, horizontal, and Star integration systems. The OS security system has to be of high performance and of considerable efficiency (Sherif, 2010). The use of the prioritization methods does not show prioritization of the order used but rather depend largely on the evaluators role and the situation that the integration systems will be employed. In this case, the banking sector seeks to employ the most effective system integration strategy in its OS security system aimed at improving the banking data security and communication performance. The first quality assurance evaluation method that will be used is systematic inquiry. In this system, evaluators will be required to conduct systematic inquiries that are data-based on the Star, Horizontal, and Vertical integration system expected to be employed on the banking OS security system. In order to achieve this goal, quality collection of data regarding merits and demerits of utilizing any of the integration systems will be done. In the 24 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT25 process of evaluation, a defensible choice of the indicators will be done so that the most credible of the enterprise integration option is identified (DelaHostria, 1997). The importance of systematic inquiry is to ensure that credibility of each system is realized and the compactibity of its integration to the banking OS Security system is determined. The collected findings will be evaluated and their credibility determined from an evidence-based approach so that the validity and reliability of the integration system can be determined (Sherif, 2010). The systematic inquiry system also looks at evaluating the choice of methodology employed in enhancing the OS security system (Sherif, 2010). The methodology has to be consistent and reliable in providing dependable data that can guarantee the success of enterprise integration system to the OS security system. In addition, there is criticality in the utility of the findings in ensuring the success of the OS security system for the banking sector. For example, the obtained information of system integrations and their validity has to be timely and comprehensive with the guarantee that it will serve to provide full and maximum benefits and reliable use to all stakeholders for the realization of value for their money. The second aspect to be evaluated will be competence. The stakeholders expect competent performance for the integration system that gets incorporated in the designed OS security system. As a result, evaluators have to spend thorough scrutiny on competence. Taking these aspects to consideration, the evaluation teams will be required to outsource and draft a number of competencies that form appropriate combination. This will ensure that the required and appropriate expertise is availed for the evaluation process. Most importantly, the aspect of competence is aimed to ensure that evaluators execute their duties within the scope of their capability as mandated. The issue of competence is fundamentally being evaluated to ensure that the integration of either Vertical, Horizontal or Star enterprise integration systems to the OS 25 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT26 security system for the banking sector, is of at most success. The system integration must be efficient, reliable, cost effective and meeting the ultimate objectives of the project which include upgrading information data security for the bank and its customers. Secondly, it is a system that will streamline internal communication within the bank’s departments. Therefore, valuators have to be competent enough to meet these aspects as they work closely within the scope and ensure mitigation of incompetence (York & MacAlister, 2015). The other evaluation methods that will be employed on the Enterprise integration systems in question awaiting selection for incorporation with the OS security system will be Honesty and Integrity of the systems. While conducting the evaluation of the three systems, evaluators are expected to be honest and throughout the entire process. The room for bias and false information should be avoided so that the three principles of integrity of the integration systems can be realized. These principles include transparency, independence, and impartiality (DelaHostria, 1997). Quality assurance for evaluation of the three Enterprise integration systems will be done base on the three evaluation methods that will see to it that the best selection is made. Quality Assurance Evaluation Methods Employed Considerations Systematic Integrity and Inquiry Honesty Competence Rating Score Rating Rating Rating Score compatibility 2 3 1 2 1 6 Efficiency 3 2 1 3 2 6 Maintainability 2 3 1 1 2 8 26 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT27 TOTAL 7 8 3 6 5 20 Weight: Each quality factor being evaluated will be assigned some weight based on its importance during the selection of the enterprise integration systems and their incorporation to the OS Security system for the bank Compatibility: 1 Efficiency: 2 Maintainability: 3 Rating: the use of rating is to make a representation of each method based on the quality factor that is being evaluated Score: the weight and rating product will translate to the score assigned to each quality or attribute under evaluation Apparently upon evaluation and based on the above matrix, competence evaluation methodology is the best since it has recorded a high score of 20 when compared to integrity and honest, and systematic inquiry. Evaluation methods employed: Systematic Inquiry: experimental results were used as a basis of the evaluation process Integrity and Honesty: any evaluation done was based on the integrity and honesty of the evaluators as well as the Enterprise system itself Competence: evaluation was based on overall competence of enterprise integration systems in question as well as that of the evaluators Some of the quality considerations included compatibility, efficiency and maintainability. 27 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT28 7. Proposed System Integration Components Architecture System Integration The system integration process may occur at the data, method, interface, hardware, and process levels. It presents how the software components seeintegration. The integration should occur on various modules of the information system such as in computers, Intranet and the Internet where each zone requires different kinds of security. Data integration The process of integrating existing data to the testing platform involves profiling and auditing the source via numerous processes that may include transformation and cleansing as well as matching data with that of the target. The process requires to be extremely flexible and scalable, need negligible technical skills, and be easy to perceive such that the enterprise and technical personnel may work in harmony. The users of the System should be able to deploy sophisticated enterprise rules for data integration and migration without necessarily requiring specialist training. System integration Steps Step 1: Planning The initial step is to describe what is attainable in regard to what the data services will cover as well as what is within reach. With the data integration scope refined, a project plan with timeline its associated resource plan and budge cost t may be set. The main objective is to integrate all the required data and components needed to run the expected system effectively as well as filter out any excess data. Due Diligence-In depth analysis of the existing system source data and components will be undertaken in close association with the enterprise users who are directly impacted by the data and component integration process and have a clear understanding of the history, current and future business issues. Budget and Timeline-The estimates will entail the timeline, hardware and software costs, profiling of data and components, creation of mapping specifications, development of data and components transformation and cleansing rules as well as loading and testing of software, data and hardware components. A realistic timeline should be set based on external dependencies as well as incorporating proper levels of contingency. Step 2: Understanding the integration components Top-Down approach The project manager will apply a top-down approach rationale to appropriately prioritize decision in the project scope in respect to the value of the enterprise, utilizing criteria like the line of business or region. By refining these components saves time and effort. Having identified the architecture components, profiling and auditing may commence to check the data and component of all potential sources to comprehend the data and determine what needs to be integrated. This step should detect any possible conflicts as well as resolve any existing problems and gaps. The profiling will enable the creation of a 28 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT29 major repository for all analysis, irrespective of the source system. The process will determine any unknown data problems, identify any inconsistency across the data and components to be integrated and assess its effect on the entire integration project (Laszewski, Williamson, &Nauduri, 2011). Step 3: Cost/Benefit Analysis All data and component parts marked for the integration have both cost and a benefit and therefore rigorous decisions should be made regarding the of source of information and components to be included or omitted from the integration. For instance, the inclusion of historical data may greatly inflate the project costs. This analysis will allow mapping specifications to be based on full knowledge and in turn result in fewer iterations of the test phase. Step 4: Executing This step will involve data extraction from the existing/source system, data transformation, cleansing and loading into the target system utilizing the set Integration rules. Step 5: Testing There are various kinds of testing and methods for testing that the enterprise should use. These methods and procedures used to conduct the testing include: Testing There are various kinds of testing and methods for testing that entreprise should use. These methods and procedures used to conduct the testing include: Integration Tests Integration Test Description Application integration Test theSystem Integration applications that access backend databases and ascertain that they perform as desired and that access and script configuration settings are properly set. Stress/load testing Measure the System Integration progress via collaboration with a replica of the software and hardware in a lab environment so as to provide live load simulation on the enterprise servers. Performance monitoring and tuning Monitor the System Integration performance Security functionality Test the different possible incremental modifications of the System Integration system to ascertain that security functions as desired in each event. Create tests to exercise the system functionalities from each secured system component. Test the System Integration Architecture security against intrusion. Integration Application Tests Application Test Description Load/stress testing Test the number of simultaneous 29 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT30 users the System Integration application may support. Ascertain that CPU and memory resource utilization levels are acceptable under high load performance. The project team may use the Enterprise Application Stress Tool, for stress testing multitier applications. Performance testing It involves testing application performance under different conditions. Also, testing overall performance impact of the System Integration application on the enterprise servers. Integration challenges when defining Implementation Framework Most system integration projects are delivered late with over budget and result in less than high-quality products. A remedy to this common problem entails the development of formal methodologies to software process improvement and maintenance as well as the application of formal project management approaches to plan, monitor, and control project resources. The continuous changes on project teams to more diverse, geographically distributed environments due to technology enhancement has led to the emergence of new challenges to the traditional system integration Project Management methods (Talla, &Valverde, 2012). Some of the challenges include: Inadequate documentation for what is required Unrealistic project deadlines, budget, and specifications Inadequate information regarding the organizations operations Some personnellevel of responsibility may increase since the new integrated system is more difficult to correct integration incompatibilities. The implementation requires new approaches to data and component reporting and therefore new procedures and operations have to be determined Other system integration challenges that were highlighted by defining the framework involve; System Integration may begin late due to late software and service components, leading to flawed and immature product execution. The Integration may begin when the hardware and software are ready, so it utilizes the current hardware and software for all operations. System Integration is anticipated to happen instantaneously; providing less an or incomplete test process so as to recover task schedule and meet the set delivery timeline. System Integration emphasizes the components instead of the system functionalities a case where the Integration team does not fully comprehend the entire system concepts. System Integration hardware components and Network Resources The support equipment for the implementation includes client/server database deployed on a LAN, a network IDS such as SNORT, and test programs that establish the functioning of the database and LAN (Sheldon, 2014). Besides the database system, there are other kinds of hardware needed for the System Integration. They include; Web Server Administrative Tools Workstation/Server Business Objects Server (may be optional) 30 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT31 Job Server The implementation will need at least four distinct physical computers for production activities.ie. a dedicated Web, Job, Business Objects Servers, as well as a database server. Client Ethernet Cable Internet Connection VGA monitor with a resolution of 1024 x 768 4GB RAM Web Server 8 GB or higher RAM Intel® Core-i3 processor or higher 1 TB system drive + 50GB drive Job Server Intel® Core-i3 processor or higher 8 GB or more of RAM 1 TB system drive + 50GB drive Business Objects Server (which may be optional) Intel® Core-i7 processor 16 GB of RAM or a higher RAM 1 TB system drive + 50GB drive (SAN storage supported for file store) Administrative Tools Server The Administrative tools may be located on either the Web or Job Servers but it may also be located on a different server machine or on a workstation that is connected to the database system. 250 GB of hard drive space Intel® Core-i3 processor or higher 8 GB or more of RAM Software Requirements The software requirements needed for theSystem Integration include; Client computer that has a browser that allows user to access the applications interface Business Objects Server (which is optional) Web Server – hosts the System Integration application and hardware components Job Server – hosts the job server software and hardware components 31 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT32 8. Implementation Framework Application Architecture The other level of the System Integration Architecture describes the major applications required for data management as well as business support. The System Integration Architecture describes the main functional elements of the architecture that ensure proper access to the data in real time, correct format and at minimal cost. The Application Architecture not only proposes the application used to implement the integration also provides a methodology; Enterprise Architecture Planning that describes it from both informational and business requirements. Hardware Architecture This architecture describes the components that anchor an environment for the application development and deployment. At the hardware architecture level, the main technological procedures are determined. These concepts include technologies that deploy applications, that support inter-process communication and data storage. At this level, the hardware architecture should be a coherent and intuitive representation that defines the hardware requirements in a systematic, coherent way. Nevertheless, it brings in new concepts that are not covered by any standard. A proper system integration will need high-level skills and experience. The Software Architectures It describes the conceptual software architecture for the system integration. It is supported by the Open Group Architectural Framework in regard to design and evaluation. The framework gives the methodology for system integration as well as the software taxonomy and software architectural standards for the integration, especially at the hardware level. The Open Group Architectural Framework gives a technical reference model that describes a taxonomy for consistent, coherent, hierarchical definition of the services offered by the software platform such as data management, network security, operating system security, transaction processing, as well as system administration. It follows that the framework also offers various architectural qualities that are intrinsic to the architecture description. These qualities may include and not limited to performance, usability, adaptability and portability as well as availability among others. Nevertheless, the TOGAF framework has numerous drawbacks. The most significant one being it emphasizes on the hardware architecture and fail to address the informational or application architectures. This framework supports a limited set of concepts and principles instead of firm modeling blueprints. Therefore, it is inadequate for modeling System Integration Architecture in a global and cohesive manner. 32 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT33 9. System Integration Implementation Plan TBD 33 SYSTEMS INTEGRATION OS BANKING SECURITY PROJECT34 References Abrahamsson, P., &Oza, N. (2010). Lean enterprise software and systems (1st ed.). Berlin: Springer. Cameron, R., Woodberg, B., Giecco, P., Eberhard, T., & Quinn, J. (2010). Junos Security. DelaHostria, E. (1997). Enterprise System / Control System Integration Scheme. Enterprise Engineering and Integration, 34-44. doi:10.1007/978-3-642-60889-6_5 Hambling, B., &Goethem, P. (2013). User acceptance testing (1st ed.). Swindon, U.K.: BCS. In Vacca, J. R. (2014). Network and system security. Laszewski, T., Williamson, J., &Nauduri, P. (2011). Oracle Information Integration, Migration, and Consolidation (1st ed.). Birmingham: Packt Pub. Sherif, M. H. (2010). Handbook of enterprise integration. Boca Raton: Auerbach Pub./CRC Press. Silberschatz, A., Gagne, G., & Galvin, P. B. (2013). Operating Systems: Security. Retrieved from https://www.cs.uic.edu/~jbell/CourseNotes/OperatingSystems/15_Security.html Talla, M., &Valverde, R. (2012). Information systems reengineering for modern business systems(1st ed.). Hershey, PA: Business Science Reference. Tran, T. A., & Park, J. Y. (2014). Development of integrated design methodology for various types of product — service systems - ScienceDirect. Retrieved from http://www.sciencedirect.com/science/article/pii/S2288430014500048 York, T. W., & MacAlister, D. (2015). Electronic Security System Integration. Hospital and Healthcare Security, 459-504. doi:10.1016/b978-0-12-420048-7.00019-2 34
Purchase answer to see full attachment