Time
10 hours 32 minutes
Difficulty
Beginner
CEU/CPE
11

Video Transcription

00:00
Welcome to Cyber is video Siris on the Company, a Security Plus certification and Exam. I'm your instructor, Rahm Warner.
00:08
In this video on security plus section 3.5,
00:12
I will summarize secure application development and deployment concepts
00:17
with an increasing number of companies welcoming the idea of developing their own APS in addition to person purchasing record numbers of ABS and incorporating open source code into their own software.
00:29
The risks and vulnerabilities associate ID have also arisen.
00:33
Security professionals need to be well versed on application security. Best practices.
00:39
That's what I'll be covering in this video.
00:42
The next few minutes we'll discuss the following topics on application security
00:48
development, lifecycle models, Secure Dev Ops, SEC Dev Ops
00:54
version control and change management. Provisioning and deep provisioning, secure coding techniques and coat quality and testing.
01:03
This is a large topic area that could easily be its own video. Siri's and certification.
01:08
You take additional time to review your study material and resource is
01:14
no amount of network hardening. Auditing or user training can compensate for bad programming.
01:19
Solid application security is essential to the long term survival of any organization
01:26
application. Security begins with secure coding and design,
01:30
which is then maintained over the life of the software through testing and patching.
01:36
There are two primary software development Life cycle or S. D. L C model she should be aware of for security, Plus,
01:44
the first is the waterfall model. This is the more traditional of the two
01:48
that walks through each phase one by one. Each step by itself starts with requirements gathering than design of the product
01:57
implementation, coding,
02:00
testing, verification, deployment and maintenance.
02:04
Each stage is completely self contained and completed in order.
02:09
Hopefully, you see there are challenges associated with it, especially waiting for testing until after development,
02:15
when it could be too late to fix major challenges. This has been solved with the agile method
02:23
agile works in cycles, with each cycle producing specific delivery. Bols. Each cycle has its own phase of requirements, design and test IQ. Much more modular, an approach.
02:36
It's also a type of rapid prototyping through repeated processes.
02:40
Methods for agile development includes scrum adaptive software development, crystal featured driven development, dynamic systems, development method, lean software development and extreme programming
02:57
rather than developers handing off buggy software to an I T. Group. It saying It's your problem now,
03:04
Dev ops developers working with operations asked developers to take responsibility for software all the way through production
03:14
secure. Dad Bob's takes that paradigm one step further to ensure that developers air using APP security testing to deliver software that it's free, or at least minimize, is the number of vulnerabilities
03:25
from Day one
03:28
from a Secure Dev Ops Perspective, software should be developed and maintained, so it's secure and resilient.
03:37
These concepts are built into secure development and operations, also known as DEV Ops,
03:44
where security is integrated into the developers operations, including their database design programming and how it works within the company's infrastructure,
03:53
it's incorporating security practices into the entire software delivery cycle.
04:00
It addresses security concerns at the beginning of projects where it's a lot quicker and easier to solve them.
04:05
And it provides added automated security testing techniques.
04:11
On your screen, you see other ideas associated with Secure Dev ops,
04:15
including continuous integration where security is every step
04:19
of the development, S. D. L. C.
04:23
Automating security through repeatable scripted tasks. Base lining as we've discussed in previous video where you have reference points that require completion and approval of said of predefined project requirements to prevent uncontrolled change
04:40
and reduce the number of vulnerabilities
04:43
immutable systems, meaning that no changing to the systems should be allowed. They maintain known, documented and repeatable configuration setting
04:53
and lastly, infrastructure as a code were I A C.
04:57
This is programmable infrastructure.
05:00
Infrastructure configuration is included with the application code.
05:04
You should refer to your own study material for more information on Secure Dev ops.
05:11
As a cyber security professional, you need to be aware of how code is compiled and run within operating systems.
05:18
They're two primary methods. One is compiled code, the other is run time,
05:24
and these are the methods for creating running excusable Could
05:30
compiled code uses a compiler program such a C or C plus plus,
05:36
while run time code uses an interpreter
05:41
so compiled versus interpreter. Code interpreted code.
05:46
Example is java or dot net
05:48
interpreted code tends to be faster
05:51
but less secure.
05:54
Another concept you need to know for security plus is change management and version control. These go hand in hand, and they control and manage software Changes needed for both quality and security
06:09
version control or source control. Prevents tampering or changing of the source code or execute a bles. Your source code should be be maintained in its own secure repositories.
06:19
Any changes to the production code needs to go through specific version control,
06:26
where you might have checks for security and quality.
06:30
Version control also tracks software life changes. Our application code changes so no changes are made by accident or surprise.
06:40
Version Control also uses distributed storage for codes such as Get get hub or subversion.
06:48
The benefits of having a robust change management and version control system is that there's historical data on changes to files, so you know who made what changes went.
07:00
Another benefit is branching and merging capabilities. You see a capability within an application you can branch it were merged them together to create a successful software package.
07:12
Lastly, traceability. You know who made what changes when, where and how.
07:17
Provisioning and d provisioning or two additional concepts you need to be aware of associating with applications security
07:25
provisioning is the creation or update of a resource.
07:29
De provisioning is the removal of the resource
07:31
provisioning in deep provisioning are part of the organizational lifecycle management and can affect any number of assets, software provisioning and deep provisions are generally automated processes in which the software packages air made available to computers and users through a self service portal.
07:48
Additionally, provisioning can be integrated with other technologies.
07:53
This is especially true for cloud based environments, benefits of provisioning and D provisioning, including the reduction of application environment processing time, an increase in developer productivity's improved capacity and significant cost savings.
08:11
Security must be implemented from the very beginning of the software development life cycle and be included with every phase in every step of application development.
08:22
In the early design phase, potential threats to the application must be identified and addressed.
08:26
Organizations must have must take into consideration ways to reduce the associated risks. Over the next few slides, I'll walk you through some secure coding techniques that you need to be familiar with and work with your application developers to make sure they are also familiar with these techniques.
08:46
These objectives can be accomplished in a variety of ways, such as threat modeling, mitigation, planning, analyzing potential vulnerabilities and attack vectors,
08:54
and secure coding within the application development life cycle.
09:00
The first consideration is authentication.
09:03
How does your application authenticate Neto authenticate toe a back end database
09:09
concept to remember is no hard coating any user. 80 your passwords user credentials into the code.
09:16
Also, be aware of how cookies are enabled within Web applications.
09:20
Proper error handling also needs to be a consideration.
09:24
Errors that are generated should be generic, not dive, old specific system or application information. Additionally, comments should not be made visible in the end user product
09:35
exception. Handling should log the air and provide the user with a standard message.
09:41
Input into applications is often in avenue into exploiting vulnerabilities associated with them.
09:48
Input validation tests whether an application properly handles input from a source outside the application that is destined for internal processing.
09:58
The most common result of improper input validation is buffer, overflow exploitation or cross site scripting
10:05
additional types of input. Validation Aires result in formats during in denial of service exploits,
10:11
and there should be a use of default values and character limitations for input Validation.
10:18
Normalization is the conversion of data to its anticipated simplest known form.
10:24
Applications often accept untrusted input strings and instead used techniques such as validation methods and input fit filtering.
10:31
These methods are based on strings character data and are similar to blacklisting, although they're not really sufficient for complete input, Validation and sanitation. Thes methods do provide some level of security
10:45
stored Procedures are most often associated with databases and database queries. Maybe a combination of pre compiled sequel statements stored in the database that executes some task
10:56
stored procedures can also be used for security by encapsulating certain logic and server side persistent modules
11:05
to increase security and reduce sequel injection vulnerabilities.
11:09
Data manipulation statements such a select and delete their sequel type statements selector Delete have to go through stored procedures before returning data.
11:20
This provides a safe use of sequel
11:24
code. Reuse its re using existing software modules, which can prove to be very efficient. The challenge with security is if those modules have not been tested prior to being put into use.
11:37
So therefore, reuse code should be validated for vulnerabilities.
11:43
Dead code is that code that no longer provides a useful function,
11:46
but there's still available within the application.
11:50
It should be removed.
11:52
Last lease, the idea and the use of third party libraries and software development kits.
11:58
I know where your source code is coming from On Li Yu's source code from a trusted location should also check for vulnerabilities associated with your third party, get libraries and software development cats
12:13
Code signing leverages a certificate based digital signature associated with the code.
12:18
The most common example of code signing his drivers.
12:22
For example, by default, Microsoft Operating system blocks the installation of unsigned drivers.
12:28
Code signing consists of signing executed bols using certificate based digital signatures. This is done to provide trustworthiness in the execute a ble code.
12:39
Another secure coding technique
12:41
is to limit the exposure of data. Any sensitive data should always be encrypted at rest in transit and what's being processed.
12:50
This is accomplished through encryption, using standard encryption algorithms, hashing and digital signatures.
12:58
I talking length about digital signature certificates, P k i in a different video.
13:05
Also leverage T. L s transport layer security. For that encryption over the network
13:11
could obvious cation and camouflage is a way of hiding the back end code. It's been used for a long time and interpreted languages.
13:20
This is often done by shortening function, invariable names and removing white space.
13:26
The best way to see the prevalence of this technique is the view the source code of a Web home page, such as Google
13:33
camouflage can predict software from reverse engineering.
13:37
Fake source code is created by modifying a piece of the original source code.
13:41
When an attacker analyzes the program, the attacker sees the fake code,
13:46
but the program executes the original one. It is run.
13:50
Use of these techniques can affect the functionality of the software programs,
13:54
so be aware how you're leveraging obfuscation and camouflage
14:01
memory management optimizes performance by assigning blocks of memory to various processes and programs.
14:09
It makes sure that sufficient memory is available for any current running program or process.
14:15
Memory management is used in all computing functions and plays an integral part in programming applications.
14:22
Programs are written to request blocks of memory, and the Allocator is used to assign that block to the program.
14:30
When the program no longer needs the data in the allocated
14:33
memory block, the blocks can then be reassigned.
14:37
Vulnerabilities may exploit and proper memory utilization
14:41
such as a both buffer overflow.
14:45
Suggestions for mitigating vulnerability, such as buffer overflows, include verifying that the buffer is on Leah's large as needed and as specified,
14:54
use input output control for data that is untrusted,
15:00
properly free allocated memory upon completion of the functions
15:03
and do not use known vulnerable functions.
15:09
Clearing sensitive information stored in memory to avoid unintentional, unintentional disclosure should also be included in memory management. Best practices.
15:18
The last concept associated with a secure coding. Our service side versus client side execution and validation
15:28
client side validations were enter. Data is validated by a script on the user's browser
15:33
before the form is sent to the servers. You validate at the end point that the data is true as opposed to server side validation, which occurs on the back end, say, Web server housing the application code.
15:46
This protects against malicious attempts by the user to bypass any input validation.
15:54
Be familiar with each of these secure coding methodologies and techniques.
16:00
The number one resource for understanding applications security. It's a wasp o W. A s p dot org's the open Web Applications Security project.
16:11
Every few years they public they published their top 10 Web application vulnerabilities.
16:18
They also provide great advice on how to exploit those vulnerabilities so you know how to protect it within your application source code.
16:26
I highly recommend checking out a wasp dot or GE for more information on applications security
16:33
in this video, I summarize secure application development and deployment concepts.
16:37
Let's practice on a few sample quiz questions.
16:41
Question one.
16:42
Which of the following will be the most secure way to deploy a legacy application that requires a legacy operating system?
16:52
The answer is
16:52
a sand boxing
16:55
creates a separate environment for that application
17:00
question, too.
17:02
Alice wants to reduce the probability of sequel injection attacks against the company's Web server.
17:07
What secure development measure would work best?
17:12
The answer is
17:15
be input validation the only answer,
17:18
which will prevent sequel injection by scrubbing the input.
17:22
This concludes the video for section 3.6 on secure development in deployment concept, view your study material form or information.

Up Next

CompTIA Security+

CompTIA Security Plus certification is a great place to start learning IT or cybersecurity. Take advantage of Cybrary's free Security+ training.

Instructed By

Instructor Profile Image
Ron Woerner
CEO, President, Chief Consultant at RWX Security Solutions LLC
Instructor