5 hours 49 minutes
Hello, everybody, and welcome to the I T Security upset number 3 80 sub would develop a life cycle. My name is Alejandro Gonna and I'll be instructor for today's session.
Learned oddities of this module is to understand and be able to identify the main faces and concepts off Nancy's up for development Life cycle.
One of the fundamental task that when you as you begin, your element of off our integration effort is to select your development methodology and you know how to enhance that Max Italy e into more security conscious one.
To do that, you can use the, you know, building security in maturity model.
Ah, that. Let's do you understand the security practices
main implemented by peers of randy stations?
You know, security
can be used in an adieu, um, fashion or RG development.
when selecting a development methodology considered that security must be built in in from the beginning of the process to ensure that security, safety and privacy requirements are selected correctly on their traceable true
development. On update of the A T device on infrastructure
to Durst, you know their comm plates. Uh, our approach is available that can be applied
to any development effort. Some well known models are, you know, Cascade spiral, extreme problem ing prototypes scrum. You know, this cousin named in detail will take forever, but most of them sure, the same faces
which our information gathering to shine development, implementation, testing and maintains
many 80 products on systems will be developed using agile Matt methodologies and want to say agile item that it contains several up. You know, it is the name for several methodologies. Are, you know, developer side using Because they're fast
given that, you know, because they have the ability to quickly designed well features on the fly, you know, and as the customer request, um, so the agile, uh, defines a number of principles some which you know, President,
you know, they have difficulties
to the interest since off security approaches, for example, developers have to deliver working suffer margins frequently
within a few weeks most of the time, So they're, of course, will focus on creating functional or business Britain modules focusing to make things work or not necessarily work in a secure fashion.
It is difficult to address this requirements in a short development cycle. Also, focus on security, Chris is that you know the velocity that they can, you know, that can be applied to functional user requirements in agile development.
So basically, they're function are great and, um,
modules as fast as they can. They're they're not actually thinking that security.
So they you know, a solution for business may be using the threat. Modeling approaches can help you with this problem. You can start by defining functional security requirements that must be integrated into the product or service.
You can turn these functional secure garments into the stakeholder requirements.
I'm not them on the product this time. At the beginning of the process, for example, you can say stuff like as a user, I want to ensure that our access passwords are off my device or the cloud servers are strong. So this becomes security requirements in ST
into a state All the room apartment
or functional apartment
assay user, for example. As a user, I want to be able to track my auntie devices authorized usage.
Another temple is as a user. I want to ensure that they that data storage in my auntie device isn't gripped.
So these bull force any development lifecycle to actually include security from the very beginning. That's a huge win for us. Remember, at the break of bats is the threads risk. An amount of money you need to spend to fix them. Increases exponentially so it's not the same. Two. Actually
focus on a security control from the better beginning at the product
and to focus on the security control or a secure if it's at the very end of the brain or even after implemented.
we can, you know, us UT also concerned with safety.
I know the security developers. You also consider additional faces like that disposal off the edge, devices off even the result of using their devices incorrectly or for longer or for a longer Peter of time. Maybe sending on alert to the server to discontinue the service if advices
any kind of kind of malfunction or is being used far, far
above, off his off, you know, the deputy life fun lifespan.
So that's something that the developers you should should take into consideration and, you know, to perform this transaction. And when I said turn section transition smoothly, I mean performed transition from the, uh, the security mind. To the safety mind,
the first step is to create a security concept off operations,
Uh, con ups a ce we call it a document reflecting nick. You know, given the system security needs and safety needs,
uh, the security security con ups or, you know, again, concept of operations.
document provides organizations with a tool for methodically
detailing the security operations of the system.
The document should be written on maintained by statistics operator to provide a road map for systems implementers during the implementation and integrations of new I ity Sub word.
Ah, you know,
kind of condom. Sub sorry. Document can contain topics like confidentially and Terry controls authentication and no repudiation monitoring the compliance. Forensics operators, containers and disposal. Never for security integrations. Probably sending an involvement mechanisms.
So at the end, things condoms document will help us to
translate from, um, a user like
needs two more security and safety needs. For example, as we told a little before these condoms, Duckman will contain stuff like as a user. I want to increase all the data traveling between my device in the cloud, for example. So this will cut, give comments, document will help us
so to both the developer and the security and safety engineers.
Understand how the new software and the new I T goodbyes must function in a secure fashion
mentioned to support a woman. Lifecycle Mental values Waas There's a bunch of little use other that all this one is the cascade
It was it was is really old, and it is not flexible at all. And the news one, I guess it's from our, you know, a student programming or any agile
worries. B s i m m. Well, as I said, the beginning is a building security in maturity model. Andi, let's do you understand the security practices being implemented all performed by beer organizations?
Where is ka tops? Well, it's, ah, document that you can use to put all the security stuff in there for your new development life cycle. You can even use this to the development life cycle, meaning the hard work, part of the physical part of the device.
And it's it stands for concept concept of operations
mentioned at least two topics that comments document should contain or confident Shallow and Terry Foreign six. Never security rations are monitoring compliance, authentication and no repudiation.
And I know I went way about the two requesting this question
in today's reelection with this cause, the main topics behind a 90 suffered development life cycle, which at the end, calls and we can Also some of them can also be applied to the development life cycle, meaning the physical that chips integrators
everything that is physical to Lady Bice
supplements materials won't you can go to any of these links. They have really, really useful information, and you should definitely check it out.
Looking forward in the next video, we'll review the main concepts off a 90 identity and next management solution.
Well, that's it for today, folks. I hope you hear the video and a T shirt.