3 hours 37 minutes
Welcome to the cyber very D mystifying PC idea, says Compliance Course.
This model will focus on the goals of the PC idea SIS and the requirements associated with them.
This video introduces you to requirements. Six.
We will talk about the requirements associated with maintaining secure systems and applications in the CD.
The learning objective of this video is to discuss some of the ends and outs of each of the mandates associated with maintaining secure systems and applications in the CD.
A lot of the meat and the goal of maintaining a vulnerability management program comes in Requirement. Six. Developed and maintain secure systems and applications.
This grouping is all about identifying and prioritizing the vulnerabilities that are associated with your CD
PC. I also wants to make sure you have in place procedures to securely develop the applications that running your environment
for software and systems that are being developed by a vendor. You need tohave secure processes for patching newly discovered vulnerabilities and put in place mitigating controls to limit the vulnerabilities potential. To impact the environment
for software that you develop in house, you have to have proper development lifecycle change control and make sure you address the top vulnerabilities as defined by the open Web application Security Project or a lost.
So let's start with six that one.
How are you able to identify the vulnerabilities in your environment and then assigned the more risk rating that reflects the scores that are assigned?
The easiest way to meet this requirement is to deploy a vulnerability scanner internally.
As the environment grows, it can quickly become unrealistic to try to manually track all the vulnerabilities for all of the software that is in your environment.
They're free and open source solutions to meet this objectives if you have a shoestring budget.
But if you do not want to deploy software to address this requirement, as long as you're able to show an auditor how you're tracking the vulnerabilities and applying your risk rating, it will meet this requirement.
Once of owner. Once a critical vulnerability is discovered and there is an active exploit, the iterations of that exploit explode. Within days,
the exploit becomes widely available toe hackers of the active trading or selling an underground markets.
The most common attacks are not facilitated via the fabled zero day,
but are more often and not be a vulnerabilities that are fixable that just haven't been
so. It's important that merchants employ a robust patching infrastructure that not only addresses the operating systems, but also all of the software applications that exist within the CD
PC. I mandates that critical patches be applied within 30 days of a release.
For best practice, you should try to do it, eh? You should probably do it faster.
The auditor will look through your policies and procedures to verify that this is defined and take a sample of systems to see their patch levels.
The sixth regrouping is focused on the software development life cycle of the merchant.
If you do not develop any software in house, and these requirements may not apply to you,
if you do develop in house most of these requirements of best practices anyway and would serve you to reduce the vectors of attack
well, crime at 63 that one is straightforward.
All tests and temporary accounts should be removed. Report. Before production use.
These accounts could be used at the back door or could be discovered by Attackers
so they should just be removed.
The 632 requirement is a mandate that code be checked to ensure that there is no insecure code or libraries being used in your application.
This could be either a mango or automated process, but it has to be done by someone other than the original writer of the code being reviewed.
Once again, the auditor is going to inspect the documents and interview personnel to evaluate your processes.
The auditor will also make sure that your code complies with all of the other PC I requirements.
Listed. Here is a link to the AWAS Code Review Guide to show you some of the components that should be in your code review process.
The 64 grouping of requirements is all around testing in the change control process.
A mature organization faction has controls around changes to minimize the potential of disruption due to instability associated with the change or introduction to of a new vulnerability that was not properly vetted.
Most compliance programs mandate that change control, be a part of your process and procedures,
and with good reason
changes could be the difference between previously being in compliance and now being out of compliance
changes could have a heavy cost. Do defines
the hood could have a heavy management cost.
They could change your customers experience for the worst.
So change control is all about evaluating and addressing all of these concerns as early in the process as possible.
Requirement 641 states that production should never mix with test environments.
You need to minimize the access to sensitive data.
Most developers probably don't need access to PAN data.
Second is testing could introduce instability to the environment.
As I mentioned in 641 developers don't need access to production environments.
If they do,
then there should be a separation of accounts.
The data shouldn't use the same account toe access, data and production as they used to do their development. Work
access should be continuously evaluated for need
requirement. 643 States that
you only use test cardholder data for testing.
Using live data could lead to date a leakage.
As I mentioned earlier. Requirement 644 mandates All test data and accounts should be scrubbed for being put into production
before going into change control procedures. Let me first talk about a common question.
Does every single change in the environment have to go through the change control process.
The answer's no
changes that occur regularly and its impact are commonly understood.
Do not have to go through the full process
like provisioning a user account
if you have a full process around that, and it doesn't have to be added to the bureaucracy of change control.
If you have a load balancer and you need to flip traffic to another server for troubleshooting,
that doesn't necessarily have to go through the full change control process.
What you should have is a list of common things that happen in your environment. That exit exempt from going through the change process
changes should detail what the previous state waas on, what the new state will be After the change has been implemented,
changes have to be authorized by designated officials.
Functionality testing is a big one that is commonly missed.
We're not just talking about the functionality of the application. We're talking about the functionality of the security controls,
so access controls and put validation. Encryption mechanisms are all among the things that need to be assessed as needed.
This is as applicable, of course,
so no need to test controls that are in no way impacted by the change,
but again, you need to be able to show all facets of the application that are impacted by the change.
A document. A rollback plan is crucial to your change control program.
If something goes wrong with the implementation of a change, you need to outline exactly how to roll back the changes in the event that something goes wrong or there's a negative impact.
Here's another key requirement for a managing her environment. As you operate over time
as a merchant, you have to be able to keep everything up to date as your CD evolves,
making sure all significant changes trigger an update to your documentation will facilitate your compliance efforts in the future.
There isn't a ton to say about the 65 grouping.
These requirements are all about making sure you have controls in place to protect against the top attack vectors for applications.
Exploring each of these vulnerabilities and how to protect against them are outside of the scope of this course.
But I will direct you to a wife's, a wasp site for a cheat sheet
on what each vulnerability is and how to determine if you are vulnerable.
Here's a quick look of the 10 vulnerabilities directly listed
equipment, 66 can be a confusing one.
This requirement is specifically for public facing applications.
66 gives you two options to meet it.
It wants you to either conduct a full security assessment of the application,
but this is different than a scam.
They want this vulnerability assessment to be conducted by someone who is independent of the developer of the application.
It is allowed to be an internal resource, but that resource must operate outside of the group that manages the application.
If using the internal resource, you must show how they're independent.
You must also demonstrate that this person is qualified. The conducting assessment
This person should exist inside of your S, T. L C. And the assessment should be completed before deployment into production.
The second option is that you have a public big If is that the public facing application should have a Web application, firewall or laugh deployed in front of it.
This could be implemented in software or hardware running in an appliance or in a typical server.
It may be a standalone device or integrated into other network components.
Wafts are designed to inspect the content of the application layer of an I P packet, as well as a content of any other layer that could be used to attack a Web application.
Some of the features that PC I recommend the WABBIT has is inspect the Web application input and respond by allowing, blocking and or alerting
preventing data leakage.
It should enforce both positive and negative security models
It has to inspect WEB What page content such as hypertext markup language, H demo, dynamic hypertext markup language de HTML and cascading style sheets. CSS
and the underlying protocols that deliver the content, such as hypertext transfer protocol, A, T, H, T, T P and hypertext transfer protocol over SSL https.
It needs the inspect Web service messages
The wife should inspect any protocol proprietary or standardized
or data constructs proprietary. Your standardized
that is used to transmit data to or from the Web application when such protocols or data is not otherwise inspected. At another point of the message flow,
the wife should be able to defend against
threats to the whap itself
and it should support SSL and or t l s termination.
Really, this should just be t l s termination since SSL has been replicated in the PC I mandate
and the last requirement is that all of the policies and procedures are documented and disseminated.
Auditors will ask personnel how they're trained and where they can find documentation about the anti virus solutions.
They should also verify that the procedures are being followed.
The more documents and artifacts you have,
the easier it is to prove that as a merchant, you're doing what you're saying. You're doing
all right. Quick quiz. Oh, sorry. This is a summary.
We discussed all of the mandates associative the PC I requirement six
Requirement six is all about making sure you have someone or have secure processes around the development in the management of your environment.
Okay, sure. False.
All changes are subject to the change control process.
Identified. Standard changes that are associated with normal operation do not have to go through the whole process.
You should have these changes documented with justification for your auditor.
Custom develop code must be reviewed by the initial developer, the auditor,
a second qualified developer
or the CEO.
I'd go with C on this question because it's the best answer. But technically, the CEO could work, too, if he or she was a qualified developer as well.
Security assessment of an application is the same as an A S V scan
can be conducted by the developer
can be done every five years or must be done by an independent third party.
This could be done by an internal resource as long as they are part of an independent portion of the organization.