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

Malware Damage - It is real and you need to be ready ...

  Malware, short for "malicious software," is any software intentionally designed to cause harm to computer systems, networks, or devices. Malware can take many forms, including viruses, trojan horses, worms, ransomware, spyware, and adware, among others. The dangers of malware are numerous, and it is crucial to protect yourself from malware to avoid serious consequences, such as: Data theft: Malware can be designed to steal personal information, such as bank account details, social security numbers, and login credentials. Once this information is stolen, it can be used for identity theft, financial fraud, and other malicious activities. System damage: Some malware can damage your computer system, causing it to crash or malfunction. This can result in lost data, system downtime, and costly repairs. Financial loss: Malware can also be used to extort money from victims. For example, ransomware can lock down a victim's computer and demand payment in exchange for the decrypti...

HIPAA - What is that we need to know .... Cyberawareness for a Health Care Organization

  Here is a detailed cyber awareness training for HIPAA candidates: Introduction to HIPAA: Provide an overview of the Health Insurance Portability and Accountability Act (HIPAA) and the importance of protecting patient information. Understanding HIPAA regulations: Explain the different regulations under HIPAA, such as the Privacy Rule, Security Rule, and Breach Notification Rule. Identifying and reporting breaches: Teach employees how to identify a potential breach of patient information and the proper procedures for reporting it. Phishing and social engineering: Provide training on how to identify and avoid phishing emails and other social engineering tactics. Passwords and authentication: Teach employees about the importance of strong passwords and multi-factor authentication. Mobile device security: Discuss the risks of using mobile devices to access patient information and the measures employees can take to keep the information secure. Remote access security: Explain the risks ...

Where are you on your Cybersecurity > Part 1 Evaluate your strenghts and weaknesses..

  here's a checklist to identify strengths and weaknesses in cybersecurity in a team. The user can score themselves against each item to identify gaps in their cybersecurity posture: Cybersecurity Policies and Procedures: Does your team have documented cybersecurity policies and procedures? Are they up-to-date and reviewed regularly? Are they communicated effectively to all team members? Access Controls: Do you have strong password policies in place? Do you enforce multi-factor authentication for sensitive accounts? Do you restrict access to sensitive information and systems on a need-to-know basis? Network Security: Do you have a secure network architecture that includes firewalls, intrusion detection and prevention, and security monitoring? Are your network devices, such as routers and switches, configured securely? Do you monitor and log network activity for potential security threats? Endpoint Security: Do you have antivirus and anti-malware software installed on all endpoints?...