\n \nHowever, there is a lack of education for small merchants about data security and compliance issues According to Visa and the National Federation of Independent Business (NFIB), 57 percent of small businesses do not view securing customer data as something that requires formal planning, and 39 percent say they rely on 'common sense' to keep their data safe. What these businesses must realize is that common sense is simply not enough to comply with the payment card industry data security standards (PCI DSS), which must be met by any merchant accepting credit card payments. And as more and more of the larger merchants become compliant and the high-profile breaches slow, industry attention will turn to the small merchant. \n \nPCI DSS compliance can be costly; large companies are spending millions on complex technologies to protect cardholder data. But there is good news for small merchants: depending on the method of processing and transaction volume, compliance can be achieved relatively easily and quite affordably. \n \nHere are several steps small businesses can take to work towards the safety and security of customer's data and that can also aid in becoming PCI compliant: \n \n- View compliance as a necessity, not an inconvenience. Merchants should view compliance as an opportunity to improve and verify the security of their customers' card data. \n \n- Educate yourself on PCI. Research the recent data losses and the growing acronym PCI DSS. Additional information can be found at https://www.pcisecuritystandards.org/tech/saq.htm. \n \n- Keep yourself up-to-date on compliance. Requirements and timelines for compliance are continually amended; small businesses need to ensure they are armed with the most up-to-date knowledge and equipment. This is especially important for those considering opening their own establishment, since new Level 4 merchants must be compliant by October 1, 2008. There are merchant education strategies for those independent merchants seeking reliable direction in addressing PCI DSS. \n \n- Opt for services that ease the burden of PCI compliance. When implementing your POS system; look for solutions that simplify PCI compliance by choosing a solution that encrypts card data at the 'read head' such as the MerchantWARE solution from Merchant Warehouse - to ensure sensitive customer data is never exposed. With no access to consumer credit card data or personal information businesses will automatically meet five of the twelve PCI DSS security standards, including the most intensive and costly. \n \nWhile adhering to these tips will not guarantee compliance or that a business will not be hacked, they can help forge a path towards better safety and security for customer data, while building a solid foundation for mandatory compliance requirements. And just as important is the invaluable asset of customer trust; ;putting customers' minds at ease by informing them their data is safe and secure will only contribute to their ongoing loyalty and keep business growing. \n"}]}};
const country = "US";
const language = "en-US,en;q=0.5";
const SITE_LANGUAGE = "en";
const siteName = "RIS News";
const userRoles = ["anonymous"];
const userUid = 0;
const indexName = "risnews";
window.dataLayer = window.dataLayer || [];
const data = {};
data.entityTaxonomy = {};
const contentTypes = [
"article",
"blog",
"bulletin",
"embed_page",
"landing_page",
"event",
"image",
"page",
"product",
"whitepaper",
"video",
"tags",
];
if (
routeInfo &&
"bundle" in routeInfo &&
contentTypes.includes(routeInfo["bundle"])
) {
data.entityBundle = routeInfo.bundle;
data.entityTitle = `${routeInfo.title} | ${siteName}`;
data.entityId = routeInfo.id;
data.entityName = routeInfo.author?.uname;
data.entityCreated = routeInfo.created;
data.sponsored = routeInfo.sponsored;
data.sponsor = routeInfo.sponsoringCompany;
data.entityType = "node";
data.entityLangcode = SITE_LANGUAGE;
data.siteName = siteName;
data.drupalLanguage = language;
data.drupalCountry = country;
data.userRoles = userRoles;
data.userUid = userUid;
data.entityTaxonomyKeys = {};
data.entityTaxonomyHierarchies = {};
data.parentNaicsCode = {};
data.isPro = false;
data.algoliaIndexName = indexName;
// Add toxonomy data
const taxonomies = {
businessTopic: "business_topic",
contentType: "content_type",
company: "company",
marketSegment: "market_segment",
};
const getHierarchy = (term, terms = []) => {
terms.push({ id: term.id, name: term.name });
if (term.parentTerm != null) {
getHierarchy(term.parentTerm, terms);
}
return terms;
};
const getTerms = (term, useApiId = false) => {
return { id: useApiId ? term.apiId : term.id, name: term.name };
};
const getKeys = (term) => {
return { id: term.id, name: term.apiId };
};
Object.entries(taxonomies).forEach(([key, item]) => {
terms = routeInfo[key];
if (terms && terms.length > 0) {
data["entityTaxonomy"][item] = terms.map((term) =>
getTerms(term, key === "company")
);
if (key !== "company") {
data["entityTaxonomyKeys"][item] = terms.map(getKeys);
termGroups = [];
terms.forEach((term, termInd) => {
termGroups[termInd] = getHierarchy(term);
});
data["entityTaxonomyHierarchies"][item] = termGroups;
}
}
});
data["entityTaxonomy"]["tags"] = routeInfo["topics"] || [];
// Primary Topic is either the business topic or the top tag.
if (routeInfo["businessTopic"]?.length > 0) {
data["entityPrimaryTopic"] = routeInfo["businessTopic"][0]["name"];
} else {
if (routeInfo["topics"]?.length > 0) {
data["entityPrimaryTopic"] = routeInfo["topics"][0]["name"];
}
}
// Primary and secondary entityNaicsCodes come from the MarketSegment
if (routeInfo.marketSegment?.length > 0) {
data.entityNaicsCode = {};
data["entityNaicsCode"]["id"] = routeInfo["marketSegment"][0]["id"];
data["entityNaicsCode"]["name"] =
routeInfo["marketSegment"][0]["naicsCode"];
if (routeInfo["marketSegment"][0]["parentTerm"] != null) {
data["parentNaicsCode"]["id"] =
routeInfo["marketSegment"][0]["parentTerm"]["id"];
data["parentNaicsCode"]["name"] =
routeInfo["marketSegment"][0]["parentTerm"]["naicsCode"];
}
} else {
data.entityNaicsCode = [];
}
if (routeInfo.taggedPro) {
data.isPro = routeInfo.taggedPro;
}
window.dataLayer.push(data);
} else if (routeInfo && "vid" in routeInfo) {
data.entityBundle = "tags";
data.entityTitle = routeInfo.name;
data.entityId = routeInfo.id;
data.entityName = routeInfo.author?.uname;
data.entityCreated = routeInfo.created;
data.entityType = "taxonomy_term";
data.entityLangcode = SITE_LANGUAGE;
data.siteName = siteName;
data.sponsored = routeInfo.sponsored;
data.sponsor = routeInfo.sponsoringCompany;
data.drupalLanguage = language;
data.drupalCountry = country;
data.userRoles = userRoles;
data.userUid = userUid;
data.algoliaIndexName = indexName;
data["entityTaxonomy"]["tags"] = {
id: routeInfo["id"],
name: routeInfo["name"],
};
window.dataLayer.push(data);
}
})();
Keeping Ahead of the Thief: PCI Compliance for the Small Business
Keeping Ahead of the Thief: PCI Compliance for the Small Business
Henry Helgeson, president and co-CEO, Merchant Warehouse
9/16/2008
TJX, Hannaford, Okemo Mountain and others have drawn massive attention as large merchants who have been breached and had millions of consumers' data compromised. While breaches at these large corporations certainly represent more data than that of most of the 6 million small merchants nationwide, small businesses are not exempt from having consumer credit card information stolen, or from meeting the same requirements for protection of sensitive consumer data. In reality, it is imperative that these businesses begin to see themselves as targets and put steps in place to combat data theft.
However, there is a lack of education for small merchants about data security and compliance issues According to Visa and the National Federation of Independent Business (NFIB), 57 percent of small businesses do not view securing customer data as something that requires formal planning, and 39 percent say they rely on 'common sense' to keep their data safe. What these businesses must realize is that common sense is simply not enough to comply with the payment card industry data security standards (PCI DSS), which must be met by any merchant accepting credit card payments. And as more and more of the larger merchants become compliant and the high-profile breaches slow, industry attention will turn to the small merchant.
PCI DSS compliance can be costly; large companies are spending millions on complex technologies to protect cardholder data. But there is good news for small merchants: depending on the method of processing and transaction volume, compliance can be achieved relatively easily and quite affordably.
Here are several steps small businesses can take to work towards the safety and security of customer's data and that can also aid in becoming PCI compliant:
- View compliance as a necessity, not an inconvenience. Merchants should view compliance as an opportunity to improve and verify the security of their customers' card data.
- Educate yourself on PCI. Research the recent data losses and the growing acronym PCI DSS. Additional information can be found at https://www.pcisecuritystandards.org/tech/saq.htm.
- Keep yourself up-to-date on compliance. Requirements and timelines for compliance are continually amended; small businesses need to ensure they are armed with the most up-to-date knowledge and equipment. This is especially important for those considering opening their own establishment, since new Level 4 merchants must be compliant by October 1, 2008. There are merchant education strategies for those independent merchants seeking reliable direction in addressing PCI DSS.
- Opt for services that ease the burden of PCI compliance. When implementing your POS system; look for solutions that simplify PCI compliance by choosing a solution that encrypts card data at the 'read head' such as the MerchantWARE solution from Merchant Warehouse - to ensure sensitive customer data is never exposed. With no access to consumer credit card data or personal information businesses will automatically meet five of the twelve PCI DSS security standards, including the most intensive and costly.
While adhering to these tips will not guarantee compliance or that a business will not be hacked, they can help forge a path towards better safety and security for customer data, while building a solid foundation for mandatory compliance requirements. And just as important is the invaluable asset of customer trust; ;putting customers' minds at ease by informing them their data is safe and secure will only contribute to their ongoing loyalty and keep business growing.