[av_layerslider id=’1′]

[av_section min_height=” min_height_px=’500px’ padding=’default’ shadow=’no-shadow’ bottom_border=’no-border-styling’ scroll_down=” id=” color=’main_color’ custom_bg=” src=” attach=’scroll’ position=’top left’ repeat=’no-repeat’ video=” video_ratio=’16:9′ video_mobile_disabled=” overlay_enable=” overlay_opacity=’0.5′ overlay_color=” overlay_pattern=” overlay_custom_pattern=”]

[av_textblock size=” font_color=” color=” custom_class=”]

PCI Requirement 2

Do Not Use Vendor-Supplied Defaults

Welcome to PCI Requirement 2. Did you know that vendor-supplied default information, such as account names and passwords, pose a serious threat to your organization’s security? Yes, vendor-supplied defaults might make installation or even support easier, but they also make it pretty simple for hackers to find the information needed to attack and exploit your system. How can we prevent this?

PCI Requirement 2 was created to help organizations fight hackers who try to compromise systems with vendor-supplied default information. In these videos, you will learn strategies for changing vendor-supplied defaults, implementing industry-accepted hardening standards, removing all unnecessary functionality, maintaining an inventory of your system components, and more. Click on a video below to get started with PCI Requirement 2.
[/av_textblock]

[av_masonry_entries link=’post_tag,156′ sort=’yes’ items=’-1′ columns=’3′ paginate=’pagination’ query_orderby=’date’ query_order=’ASC’ size=’flex’ gap=’large’ overlay_fx=” id=” caption_elements=’title excerpt’ caption_styling=” caption_display=’on-hover’ custom_class=”]

[/av_section]