Skip to main content

SDLC - Infosec and the SDLC - Where to implement Security

The traditional way to develop software is to write down the Software Requirements Specification (SRS) document and then bring it to the table for security to review them. It is always an after thought and it involves lot of selling from the Information Security Team to do the selling to make a few changes to the SRS.

Many a times when the SRS is written down and the Business Analyst picks up the nuances of the application to document the SRS, a major area not covered is Information Security. We have also found instances where the Information Technology folks define security in such a way that it suits their platform or technology they are comfortable with.

The major trouble with this model is that the Business Analyst is so intent on the functionality of the application and the Technologists – Architect and the Project Manger are intent on building an application in time and with budgets, that InfoSec issues are on the back burner.

The approach that is best recommended is for the Information protection and requirements to come from the business owner. We are often asked why the business owner, often by the architect, but the fact is, they as the user of the application know what is best and what needs to be protected. The Business owner also owns the application and he is the best judge as to the reasons for the application to exist in the first place. They generate the data, they manipulate the data, they understand and know what they are capturing or being used in the application. Is it not obvious they should know how to handle the information?

The business analyst needs to understand this main reason for getting the business owner to specify the requirements and capture the requirements, based on these inputs it would be prudent for the architect and the Information Security Architect to work with the available technologies and bring out the best with all the features required by the business.
The major advantages in getting the business owner involved is, this eliminates unnecessary work flows that are a product of technology and not business. The work flows are clearly understood by the business user as he is the one who had put down the specifications.
So what are the major specifications that come from the business – It does not matter how the technology would achieve the requirements , the specs may include
  • Who has access to the application, what are the roles for the application?
  • What are the approval work flows?
  • What are the requirements for audit trails ?
  • What are the requirements for identification ?
  • What are the audit trails required for reporting ?
  • What are the Security flags that needs to be notified ?
  • What are the controls required in certain fields ?
Some of the above questions are to be documented in the SRS. If the SRS does not have it , very likely that they would be ignored during the design phase. This would ensure the application is secure as well as reduce the costs of re-factoring the application later.

Comments

Popular posts from this blog

Where are we headed ... A crystal ball into Cybersecurity in the next five years .. Are we ready?

  The future of Cyber Security: Trends and Predictions for the Next 5 years The field of cybersecurity is constantly evolving, and the threats are only getting more sophisticated. In the next five years, we can expect to see a number of trends emerge in the field of cybersecurity, including: The rise of artificial intelligence (AI). AI is already being used by cybercriminals to develop more sophisticated and targeted attacks. As AI continues to develop, it is likely that cybercriminals will be able to use it to even greater effect. The increasing use of cloud computing. Cloud computing has many benefits, but it also introduces new security challenges. Cloud-based data is often more vulnerable to attack than data that is stored on-premises. The growth of the Internet of Things (IoT). The IoT is connecting billions of devices to the internet, which creates a vast new attack surface for cybercriminals. IoT devices are often poorly secured, making them easy targets for attack. The shor...

The Shifting Landscape of Knowledge and the Nobel Prize

Our recent conversation sparked some interesting thoughts about the prestigious Nobel Prize and the distribution of its recipients across the globe. Inspired by a user's search history, we delved into the fascinating patterns and potential implications of who gets recognized for groundbreaking achievements. The initial point of discussion centered on the user's search activity, which revealed an interest in various scientific and technological topics, as well as a specific search for "Nobel Prize winners by country." This led us to explore the geographical distribution of Nobel laureates, and a question arose: why does it seem that certain schools and countries, particularly in the West, have a higher representation? We considered several factors that might contribute to this observation: Historical Dominance in Science: Historically, Western nations have often been at the forefront of scientific research due to earlier investments and established infrastructure. V...

Red Team Blue Team Exercises - A Roadmap to follow to test the efficacy of controls

  Scenario 1: Phishing Attack Red Team Playbook Day 1: Send out phishing emails to the blue team. Monitor the blue team's response. Day 2: Analyze the blue team's response and identify any vulnerabilities. Report the findings to the blue team. Blue Team Playbook Day 1: Train employees on how to identify and avoid phishing emails. Monitor for phishing emails. Day 2: Analyze the phishing emails sent by the red team. Identify any vulnerabilities in the organization's phishing detection and response processes. Develop a plan to improve the organization's phishing detection and response processes. Analysis The red team's phishing attack was successful in getting several employees to click on the phishing links. This shows that the organization needs to improve its employee training on phishing awareness. The blue team was able to identify and contain the phishing attack, but it took them several hours to do so. This shows that the organization needs to improve its phishi...