Methodology

The methodology and process for establishing a comprehensive security for enterprise applications are listed in the following diagram:

  • Security analysis: The first step in security is to understand all the security requirements in the analysis phase. Organizational security policies and standards will be incorporated into the program as security requirements. Different potential risks that will be faced by the enterprise will be considered. The security team will come up with policies and designs for all identified security requirements. Security policies will outline the security measures that need to be covered in software and at hardware levels, such as ports, protocols, firewalls, and encryption standards. In this step, we will establish a comprehensive security checklist that will be used for implementation and verification by the development and testing teams.
  • Threat modeling: All internal and external threats will be analyzed during this stage. The main risks and threats for the enterprise applications are identified and modeled. This information will be used to provide recommendations to devise controls and policies. The threats will be categorized and prioritized based on the probability of occurrence and the impact of the threat. Some critical external threats include Distributed Denial of Service (DDoS), worms and Trojan Horses, phishing attacks, natural disasters. Some of the internal threats include identity theft and physical threats. An increasing trend is phishing attacks on e-mail, client-side request manipulation, and spam generated from social media websites.
  • Security design: Different scenarios for the major tenets, such as confidentiality, integrity, and availability, will be identified. Detailed security principles and security control policies will be outlined based on recommendations and assessments done in previous stages. For example, a man-in-the-middle attack scenario can compromise the information integrity, and DDoS will impact the availability. For each of the user scenarios, a security policy will be designed and mapped. Security policies will be aimed mainly at prevention, detection, and the recovery from security events and incidents. Security policies should provide comprehensive coverage for all kinds of threat scenarios.
  • Security implementation and QA: The security checklist identified in the analysis stage should be strictly followed during application development. Based on security guidelines and policies, comprehensive security measures will be implemented at all tiers and for all software and hardware components. Configuration changes should be done at the server end to enforce the prescribed policies. Different static code analysis tools scan the code for potential security issues and should be leveraged. Similarly, black-box penetration testing tools and scripts should also be used for uncovering application vulnerabilities. Internal and external ethical hackers and security experts should be engaged in carrying out sophisticated security tests and vulnerability assessment.
  • Security monitoring: Security is a continuous and ongoing process, and therefore, even after the application is deployed, the application should be closely monitored for all kinds of security incidents and events. Security policies and patches must be updated on a timely basis for maximum protection.

The security establishment process is shown in the following diagram:

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset