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.
Labels:

Comments

Post a Comment

Popular posts from this blog

The Convergence of Epistemologies: Mapping Quantum Physics to Ancient Indian Thought

The "Retrofitting" Fallacy A common critique from Western academia is that modern Indians suffer from "post-diction"—waiting for quantum physicists to make a discovery and then conveniently shoehorning it into a vague verse from the Upanishads . This critique relies on a fundamental misunderstanding of both language and methodology. The ancient seers ( Rishis ) were not writing religious poetry or mystical metaphors; they were writing cognitive science, cosmology, and metaphysics in a highly technical, high-context language (Sanskrit). When 19th-century colonial translators—who operated strictly on a Newtonian, binary, mechanical worldview—encountered these texts, they did not have the scientific vocabulary to comprehend them. They translated precise technical terms into crude religious dogma (e.g., Maya into "illusion"). Today, we are not "retrofitting" the old books to match new physics. We are finally acquiring the scientific vocabulary requi...
Post a Comment
Read more

The CyberRange Exercise - What it entails and Why?

A cyber range exercise is a simulated cyberattack that is used to train cybersecurity professionals. Cyber range exercises can be used to train a variety of skills, including penetration testing, incident response, and threat hunting. Cyber range exercises can be customized to fit the needs of the organization or team. For example, an organization that is concerned about ransomware attacks could create a cyber range exercise that simulates a ransomware attack. The size of the team that participates in a cyber range exercise can vary. Some cyber range exercises are designed for individuals, while others are designed for teams of up to 100 people. The roles that the team members play will also vary depending on the exercise. Some common roles that team members play in cyber range exercises include: Attacker: The attacker is responsible for trying to exploit vulnerabilities in the system. Defender: The defender is responsible for defending the system from the attacker. Observer:...
Post a Comment
Read more
CYBERRANGES - The Playground to hone your Information Security Skills   Cyber ranges are simulated environments designed to train individuals and teams on how to detect, prevent, and respond to cyber attacks. They provide a safe and controlled environment where security professionals can test their skills and practice real-world scenarios without risking the security of actual systems and data. Here are some reasons why cyber ranges are a great tool for training: Realistic Scenarios: Cyber ranges are designed to simulate real-world scenarios, so security professionals can practice dealing with various types of attacks in a controlled environment. This helps them gain experience and develop the necessary skills to handle real incidents. Safe Environment: Cyber ranges provide a safe environment for security professionals to experiment with different tools and techniques without risking the security of actual systems and data. Collaboration: Cyber ranges also promote collaboration and...
Post a Comment
Read more