Software Security

A MICRO PROJECT

Submitted in the partial fulfilment of requirements of MSBTE For

Second Year Diploma (SEM-IV) in Computer Engineering By

1. Sanika Kamble
2. Shruti Shevade
3. Purva Nakharekar
4. Shruti Sawant
5. Tanvi Chavan

Under supervision of

Prof. S. N. Mane
Lecturer in Computer Department,
Department of Computer Engineering,
Rajendra Mane Polytechnic, Ambav, Devrukh, Ratnagiri

Department of Computer Engineering Rajendra

Mane Polytechnic,
Ambav, Devrukh, Ratnagiri, Maharashtra,India,415804
2023-2024
 CERTIFICATE

This is to certify that Sanika Kamble, Shruti Shevade, Purva Nakharekar, Shruti Sawant,
Tanvi Chavan students of Fourth Semester of Diploma in Computer Engineering of
Rajendra Mane Polytechnic, Ambav (Code: 1507) have submitted the micro-project
and defended the viva-voce of the term work micro-project entitled 'Software
Security' satisfactorily in the Subject Software Engineering (Sub. Code:22413) for
the Academic Year 2023-24 as prescribed in the curriculum.

Place: Rajendra Mane Polytechnic, Ambav Date:

Ms. S. N. Mane Mr F.R.Bodale Mr. N. B. Bhopale

(Supervisor) (HOD) (PRINCIPAL)
 CERTIFICATE OF APPROVAL

This is to certify that Sanika Kamble, Shruti Shevade, Purva Nakharekar, Shruti Sawant,
Tanvi Chavan students of Fourth Semester of Diploma in Computer Engineering of
Rajendra Mane Polytechnic, Ambav (Code:1507) have submitted the proposal for
micro-project entitled 'Software Security' in the Subject Software Engineering (Sub.
Code:22413) for the Academic Year 2023-24. The micro-project proposal for
aforementioned title has been approved for its completion as per the MSBTE
instructions.

Supervisor

Prof. Ms. S .N .Mane

Leacturer in computer
Department

Date:
Place: Rajendra Mane Polytechnic, Ambav, Devrukh
 Micro Project Proposal
'Software Security'

1.0 Brief Introduction

Software security is an idea implemented to protect software against malicious attack and
other hacker risks so that the software continues to function correctly under such potential risks.
Security is necessary to provide integrity, authentication and availability.

2.0 Aim of the Micro-Project

 To understand Software Security life cycle.
 To know about Secure Software engineering.

3.0 Action plan

Details of the activity Planned Planned Name of responsible

Sr. start date finish date team member
No.
1 Finalizing the topic. 7.3.2024 7.3.2024 All group members

2 Finalizing the aim, methods and material 7.3.2024 14.3.2024 All group members
required.

3 Collection of data. 14.3.2024 14.3.2024 All group members

4 Analysing of data and extracting 14.3.2024 21.3.2024 All group members

important topic.

Discussion and finalization of the All group members

5 information required for 21.3.2024 21.3.2024
preparing the report.
6 Preparing the report. 21.3.2024 28.3.2024 All group members

7 Finalizing report. 28.3.2024 28.3.2024 All group members

8 Preparing the presentation 6.4.2024 6.4.2024 All group members

4.0 Actual resources used

Sr. No. Name of resources Specifications Quantity Remark

1. Internet Searching information

2. Mobile phone Collecting information
3. Laptop Creating project

5.0 Name of team members

1. Sanika Kamble : 02
2. Shruti Shevade : 04
3. Purva Nakharekar: 08
4. Shruti Sawant : 31
5. Tanvi Chavan : 32

Ms. S. N. Mane
(Supervisor)
 Report

1.0 Rationale
Software security relates entirely and completely to quality. Computer systems are everywhere now-a-
days and rapid development and expansion of network-based applications have changed the computing
world in the last decade.

However, this overwhelming success has a drawback, means most software-controlled systems are prone to
attacks both by internal and external users of the highly connected computing systems. These software
systems must be engineered with reliable protection mechanisms, while still delivering the expected value of
the software to their customers within the budgeted time and cost.

Software security is an idea implemented to protect software against malicious attack and other hacker
risks so that the software continues to function correctly under such potential risks. Security is necessary
to provide integrity, authentication and availability.

2.0 Literature Review

Software security is an idea implemented to protect software against malicious attack and other
hacker risks so that the software continues to function correctly under such potential risks. Security is
necessary to provide integrity, authentication and availability.

3.0 Actual Procedure Followed

First of all, we all discussed about the Topic. After that all the members collected the data of
our project. Then we have critically read all the points and analysed them and have prepared
notes. After preparation of notes took place, we all have again discuss on the points that we
have consider for project and finalized it. We have crosschecked and verified it from our
teacher. Then we have prepared the report and submitted it to teacher and then finally we will
do presentation of report during viva-voce.

4.0 Computer System

I have used DELL INSPIRON, 11th generation WITH INBUILT WINDOWS 10 Operating system of 3:20 GHz
INTEL Pentium Core i3 processor with technology computer (PC). Dell Inspiron desktops and all-in-
one PCs are designed with innovative technology and latest features.
5.0 Need of Security:

 Due to heavy dependence of computer network-based applications on various software and

software-controlled systems, software security has become an essential issue.
 Almost every software-controlled system faces potential threats from system user, both insiders
and outsiders. It is well accepted that "the root of most security problems is software that fails
unexpected ways when under attack". Therefore, software must be engineered with protection
mechanisms against attacks.
 Software should be designed with the objective not only of implementing the quality functionalities
required for their users, but also of combating potential and unexpected threats.
 The principal objectives of software security engineering, need to be reinvestigated, and a
methodology is required that can be employed for building secure software systems.
 Software security engineering is a practice to address software security issues in a systematic
manner

6.0 Core Security Properties of Secure Software:

Following are the consequences based on security basics:

1. Integrity: Verification that the information contained in the message is not tampered with,
accidentally or deliberately, during transmission.
2. Non-repudiation: There can be no denial on the part of the sender of having sent a message that is
digitally signed.
3. Confidentiality: Means that the information contained in the message is kept private and only the
sender and the intended recipient will be able to read it.

4. Authentication: Verification that the people with whom we are corresponding actually are who

5. Availability: Availability is defined as the requirements should focus on how available a resource
should be for authorized users.

Fig. depicts the stages of Software Security Life Cycle (SSLC). Recently, the most of the researchers have
shifted from a project-oriented view to a product life cycle-oriented view of software security and trying
to understand the characteristics of security demands.
SSLC Model and Security Management Framework:

• The Software Security Life Cycle is confined to project level (Fig. 5.27) has mainly four stages. The
characteristics and function of the stages are as under:

1. Introduction Stage: The users, in this stage, are those who devoted software. During this stage the major
concerns are how to make the software works. The security mechanism is concern in this stage.

2. Growth Stage: In this stage, system usage is up and the number of system attacks reported is important. As
the software enters this stage, the monitoring of system attacks and users problem reports is an
important concern. In order to manage the increasing security demand, it is critical to allocate more
programmers copying with the increasing countermeasure requests to prevent accumulating
dissatisfaction. The security tolerance is the main concern in this stage.

3. Maturity Stage: After deploying the system, the users experience the growth of enhancement requests in
the maturity phase. At this stage, the focus is enhancement of projects. Security experts are expanding the
software functions and trying to prolong the life of the software.

4. Decline Stage: At this stage, the software is easy to venerate, and attackers can easily exploit it. The
users require software renovation. In this phase, production team must choose between integrating the
software with other security mechanism or developing a substitute software.
7.0 Introduction to DevOps
 The field of DevOps has become popular and commonplace in recent years. DevOps has provided
speed and quality benefits with continuous development and deployment methods, but it does not
guarantee the security of an entire organization.
 The field of DevOps has become popular and commonplace in recent years. DevOps has provided
speed and quality benefits with continuous development and deployment methods, but it does not
guarantee the security of an entire organization.
 DevOps is a set of practices intended to reduce the time between committing a change to a system
and the change being placed into normal production, while ensuring high quality.
 DevOps security refers to the discipline and practice of safeguarding the entire DevOps
environment through strategies, policies, processes, and technology. Security should be built into
every part of the DevOps lifecycle, including inception, design, build, test, release, support,
maintenance, and beyond.
8.0 Skills Developed
1. The project helped to develop attitude of enquiry Students identified problems
and reached to its solution.

2. The project taught the skills of working as an effective team member. Every
member participated in group work and completed the distributed task in.

3. The students also leaned to work independently for the responsibility undertaken.

4. The skills of collecting the data required to solve the problem has been developed.

5. This project also taught how to analyse the data collected and how to generate
the useful information from it.

6. Every member understood the significance of target setting why persistent work
is required to complete it.

7. Problem solving skills, time management skills have also been developed.

8. The most importantly student learnt the process of preparing a report, chart and
presenting it to defence the work.
9.0 Conclusion
 Rapid progress in computer technology and software has led to the situation where powerful
packages such as MSC Mare can be used on desktop systems.
 This made it possible to study the effect of damage on the dynamics of a structure such as a blade
prior to constructing an experimental test structure.
 From this analysis it could clearly be seen that certain mode shapes were more susceptible to
damage than others. These findings correlated well with findings during a literature study.
 It was also found that the type of element used was extremely important. Higher order elements
gave superior accuracy although they were computationally more expensive.
 First order solid elements are not a real proposition due to their poor performance in bending.

10.0 Reference
 https://www.scribd.com/document/428280918/Cgr-Project
 https://projectchampionz.com.ng/projecttopics/computer-graphics-cg-project-topics-and-
materials/