[et_pb_section fb_built=”1″ _builder_version=”4.9.2″ _module_preset=”default” background_image=”https:\/\/sertalink.com\/wp-content\/uploads\/2023\/03\/purp2-1-1.png” background_position=”top_left” custom_padding=”13em||||false|false” hover_enabled=”0″ da_disable_devices=”off|off|off” custom_padding_last_edited=”on|phone” custom_padding_phone=”5em||||false|false” sticky_enabled=”0″ da_is_popup=”off” da_exit_intent=”off” da_has_close=”on” da_alt_close=”off” da_dark_close=”off” da_not_modal=”on” da_is_singular=”off” da_with_loader=”off” da_has_shadow=”on”][et_pb_row _builder_version=”4.9.2″ _module_preset=”default” animation_style=”zoom” animation_intensity_zoom=”10%” animation_starting_opacity=”100%” hover_enabled=”0″ width_last_edited=”on|phone” width_phone=”85%” sticky_enabled=”0″][et_pb_column type=”4_4″ _builder_version=”4.9.2″ _module_preset=”default”][et_pb_text _builder_version=”4.9.2″ _module_preset=”default” header_font=”Fjalla|700|||||||” header_text_color=”#FFFFFF” header_font_size=”50px” custom_margin=”||0px||false|false” custom_padding=”||||false|false” hover_enabled=”0″ header_font_size_last_edited=”on|phone” header_font_size_phone=”35px” sticky_enabled=”0″]<\/p>\n
[\/et_pb_text][et_pb_text _builder_version=”4.9.2″ _module_preset=”default” text_font=”Montserrat Regular||||||||” text_text_color=”#bfbfbf” text_font_size=”16px” header_font=”Fjalla|700|||||||” header_text_color=”#FFFFFF” custom_margin=”||||false|false” custom_padding=”||||false|false”]Homepage<\/a> \/ Data Governance & Compliance<\/a> \/ PCI DSS[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.9.2″ _module_preset=”default” hover_enabled=”0″ da_disable_devices=”off|off|off” custom_padding_last_edited=”on|phone” custom_padding_phone=”10px||||false|false” sticky_enabled=”0″ da_is_popup=”off” da_exit_intent=”off” da_has_close=”on” da_alt_close=”off” da_dark_close=”off” da_not_modal=”on” da_is_singular=”off” da_with_loader=”off” da_has_shadow=”on”][et_pb_row _builder_version=”4.9.2″ _module_preset=”default” hover_enabled=”0″ width_last_edited=”on|phone” width_phone=”85%” sticky_enabled=”0″][et_pb_column type=”4_4″ _builder_version=”4.9.2″ _module_preset=”default”][et_pb_text admin_label=”Text” _builder_version=”4.9.2″ text_font=”Montserrat Regular||||||||” text_line_height=”1.5em” header_2_font=”Fjalla||||||||” header_3_font=”Fjalla||||||||” background_size=”initial” background_position=”top_left” background_repeat=”repeat” hover_enabled=”0″ use_border_color=”off” border_color=”#ffffff” border_style=”solid” text_font_size_last_edited=”on|phone” text_font_size_phone=”15px” sticky_enabled=”0″]<\/p>\n Overview about: Payment Card Industry Data Security Standard<\/strong><\/p>\n Overview about: Payment Card Industry Data Security Standard<\/p>\n The Payment Card Industry Data Security Standard (PCI DSS) is a widely accepted set of policies and procedures intended to optimize the security of credit, debit and cash card transactions and protect cardholders against misuse of their personal information. The PCI DSS was created jointly in 2004 by four major credit-card companies: Visa, MasterCard, Discover and American Express.<\/p>\n The PCI DSS specifies and elaborates on six major objectives.<\/p>\n First, a secure network must be maintained in which transactions can be conducted. This requirement involves the use of firewalls that are robust enough to be effective without causing undue inconvenience to cardholders or vendors. Specialized firewalls are available for wireless LANs, which are highly vulnerable to eavesdropping and attacks by malicious hackers. In addition, authentication data such as personal identification numbers (PINs) and passwords must not involve defaults supplied by the vendors. Customers should be able to conveniently and frequently change such data.<\/p>\n Second, cardholder information must be protected wherever it is stored. Repositories with vital data such as dates of birth, mothers\u2019 maiden names, Social Security numbers, phone numbers and mailing addresses should be secure against hacking. When cardholder data is transmitted through public networks, that data must be encrypted in an effective way. Digital encryption is important in all forms of credit-card transactions, but particularly in e-commerce conducted on the Internet.<\/p>\n Third, systems should be protected against the activities of malicious hackers by using frequently updated anti-virus software, anti-spyware programs, and other anti-malwaresolutions. All applications should be free of bugs and vulnerabilities that might open the door to exploits in which cardholder data could be stolen or altered. Patches offered by software and operating system (OS) vendors should be regularly installed to ensure the highest possible level of vulnerability management.<\/p>\n Fourth, access to system information and operations should be restricted and controlled. Cardholders should not have to provide information to businesses unless those businesses must know that information to protect themselves and effectively carry out a transaction. Every person who uses a computer in the system must be assigned a unique and confidential identification name or number. Cardholder data should be protected physically as well as electronically. Examples include the use of document shredders, avoidance of unnecessary paper document duplication, and locks and chains on dumpsters to discourage criminals who would otherwise rummage through the trash.<\/p>\n Fifth, networks must be constantly monitored and regularly tested to ensure that all security measures and processes are in place, are functioning properly, and are kept up-do-date. For example, anti-virus and anti-spyware programs should be provided with the latest definitions and signatures. These programs should scan all exchanged data, all applications, all random-access memory (RAM) and all storage media frequently if not continuously.<\/p>\n Sixth, a formal information security policy must be defined, maintained, and followed at all times and by all participating entities. Enforcement measures such as audits and penalties for non-compliance may be necessary.<\/p>\n Any organization that handles payment cards, including debit and credit cards, must meet the 12 requirements directly or through a compensating control. However, compensating controls are not always allowed and must be approved on a case-by-case basis by a PCI QSA. Failure to meet the PCI DSS 12 requirements may result in fines or terminationof credit card processing privileges.<\/p>\n The PCI DSS 12 requirements are as follows:<\/p>\n 1. Install and maintain a firewall configuration to protect cardholder data.<\/p>\n 2. Do not use vendor-supplied defaults for system passwords and other security parameters.<\/p>\n 3. Protect stored cardholder data.<\/p>\n 4. Encrypt transmission of cardholder data across open, public networks.<\/p>\n 5. Use and regularly update antivirus software.<\/p>\n 6. Develop and maintain secure systems and applications.<\/p>\n 7. Restrict access to cardholder data by business need-to-know.<\/p>\n 8. Assign a unique ID to each person with computer access.<\/p>\n 9. Restrict physical access to cardholder data.<\/p>\n 10. Track and monitor all access to network resources and cardholder data.<\/p>\n 11. Regularly test security systems and processes.<\/p>\n 12. Maintain a policy that addresses information security.<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":" PCI DSS Homepage \/ Data Governance & Compliance \/ PCI DSS Overview about: Payment Card Industry Data Security Standard Overview about: Payment Card Industry Data Security Standard The Payment Card Industry Data Security Standard (PCI DSS) is a widely accepted set of policies and procedures intended to optimize the security of credit, debit and cash […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"class_list":["post-15289","page","type-page","status-publish","hentry"],"yoast_head":"\n