Hey, guys, Welcome to another episode of the S S C P Exam Prep.
I'm your host, Peter Simple.
This is domain to lesson three.
So far in domain to we have looked at the code of ethics, which is the minimum of required standard behavior for all SS CP practitioners. We've looked at the CIA Triad. That's the triangle of confidentiality, integrity and availability, which is
the fundamental aspect of cybersecurity.
We've looked at security, architecture, er, and how to successfully build security systems using different security practices. And we've looked at controls, the managerial, technical and operation controls.
We've taken a look at system security plans, which is a detailed document describing all of the different aspects of cyber security within a given system. And today, in this lesson, we're gonna take a look at secure development in acquisition life cycles, which is
how to securely design computer systems.
And we'll also take a look at system vulnerabilities, secure development and acquisition practices and how they relate to each other. We're gonna look specifically at how secure development reduces system vulnerabilities. And when we make this a habit,
it will be a perfect opportunity to design a secure system.
physically in actively participate in the development of a system. It is important for the practitioner to know and understand how these systems have developed.
The most popular, says Secure Development System is known as the waterfall meant
this is the one that's used in most organizations around the world.
How it works is starts up at the top of the first step of requirements,
and it can systematically goes down each level until the system is completed so it starts or requirements. And then it goes to system design, implementation, integration, deployment and finally made it.
The way the waterfall method works is it's a one way stream, kind of like having our waterfall, but you cannot go back up once you go down, so it's important to make sure everything in the current step is completed before the next step is started.
So in the first step, requirements gathering analysis, functional and non functional requirements have documented
functional requirements are user interactions and processing steps. Things that the system users will have to deal with
non functional requirements are things like performance and system constraints.
Security requirements are also defined at the first step
the next step is the system design. This is where the requirements are turned into diagrams and presented to the stake holders or people who have an interest in the system.
Once these system designs are turned into flow charts and narratives, and once they pass the approval of all the stakeholders to make sure all the requirements are there, that's when the system is actually beginning to be implemented.
Programming is done like in most places in modules real small, little
compact blocks of code, which can be easily tested, easily applied and be easily edited.
Security practitioner is responsible for the correct implementation off all the security concepts in this death.
The next step is the integration. All the tiny little modules are come together and are tested together separately and in groups to ensure that they work as expected.
Once the testing has been thoroughly done,
the system is deployed into a controlled environment for quality assurance. This is when the system is tested with test data as a whole to see how it will respond If all goes well, the system is then put into production
as always, like all system's not perfect. So as bugs and vulnerabilities or rise or come about.
They are patched up and fixed to maintain the integrity of the system.
Another lesser known method is known as the spiral method. This method is very similar to the waterfall method and that there are six different steps starting from the requirements and which go down to the maintenance
dealing difference between the spiral method. On the waterfall method, there is a little loop in each one of the steps.
Little work is known as the P D. C. A, which is the plan Do Check Act, and this group is done as many times as needed until each step is thoroughly done. So, for example, the first step to the waterfall method is where all the requirements are
here. The requirements are gathered,
everything is written down there. Check to make sure they are all there, and then they start acting upon. If the loop is needed to be done again, then it will. If not, the system designed can be started.
Another type of application development method is known as rad rapid application developed.
This is where the programmers
build very small little components and prototypes as the gap that get requirements are gathered. So as soon as they have a requirement that both small prototype for
then they modify that prototype by building another small prototype. And the system gives repeated until all of the requirements are taken care of. Now this is good, and that is good in the sense that errors or detective very early.
But if bad in the sense that you can get caught up in a building so many prototypes, you can get away from what the true purpose of the system is actually for
Another application development method, which is actually rising in popularity,
especially in universities and start up companies, is agile development. This relies on feedback from application users and development teams as their primary control. It
this is very similar, but also very different than the waterfall mended. With this, you can go down the steps, or you can go back up the steps, or you could go in a loop as many times as needed.
So how the agile method works is that the requirements are gathered and the design is started.
Then, once design has started,
the programmers who were designing the architecture, the system go back and take a look at the requirements.
And then from there they tweet the design,
and this process is continued until they have a good design, and then they start to code.
They start to code and then go back to the design, look at the design again
and continue to coach again and go back to the design and tweet the design every single time. So the way this works is
it's divided up in its time period called sprints. Each sprint is usually one week or two weeks,
so the developers like code for a week and then go back to design and take a look, show what they have to the stakeholders and then the Conus tweets.
Then they go back and code for another week,
and then they bring that new prototype back
to be looked at by the designers again. And the system is continued all the way down until the system is completed, thoroughly tested and then put into production
system vulnerabilities and secure development. Exposing applications,
infrastructure information to external users, freaks, the opportunity for compromise by bad guys who wish to steal customer data and private information
and damage on organizations reputation there. Many vulnerabilities that face Web facing applications, which provide excellent opportunities for malicious attack by unauthorized users
and turn development project should combine secure coding practices
to reduce these vulnerabilities.
Best way to participate With system vulnerabilities insecure development is too
use a loss. A loss is the open Web application security project.
This provides a freely available listing of the top vulnerabilities found and all of the Web applications. Anything that faces the wet
they list. Best practices and God lines for developers and areas of authentication. Session management, encryption of sensitive data, Adam van confirmations, air handling.
I think it's very important that everyone should be familiar with the old boss, especially if you are a Web developer or someone who creates applications that interact with the Wen.
You can check it out at this link down here in the West. A wasp it dot org's
hardware and software. More specifically, I 10 I t Asset Management.
This is the process of collecting inventory, financial and contractual baited to manage I t. Asset throughout their life cycle.
This is a very important process because it is important to know what assets you have and it's even more important to know what is on your network
unmanaged harbor assets or more likely to be vulnerable to attacks.
So if this is one your network, if you have an unmanaged asset on your network, your network is more vulnerable to attacks. So that's why it's important to know what you pass that you have in your organization
now underneath I T Asset Management or four different types of management's.
One is Hardware Asset Management, which is really anything that has an address, anything that is addressable that sits on your network hardware.
2nd 1 is software inventory management. What software programs or systems do you have running on the computers, the printers, the servers? That kind of
the third is configuration settings management.
How are these assets configured? Are they configured securely? It's very important to know the configuration of your assets because then you can determine whether or not these assets are protected or not. And the 4th 1 Vulnerability Patch Management.
When management of vulnerability is found, it can be properly taken care of. To keep your network and organization more secure, we'll be looking at these four types of management a little bit later in this domain.
In today's lecture, we discuss secure development in acquisition life cycles. That is the process of building systems securely using the waterfall method Spiro Method and the agile method. And we've looked at system vulnerability, secure development, acquisition practices,
family how, when you develop securely, it reduces system vulnerabilities
This application development model consists of six linear steps.
be rapid application development?
See spiral model or D The waterfall model
If you pick D than you are correct. Remember, Waterfall Model consists of six steps going from requirements all the way down to maintenance. It only goes in one direction, so each that must be completed before the next step is started.
Thanks for watching guys. I really hope you learned a lot. I'll see you next time.