MICRO™'s payment processing is PCI Compliant. To be PCI Compliant, MICRO™ never sees (or has access to) card data at all. All payment processing on MICRO™ is managed by PayPal. PayPal has been audited by an independent PCI Qualified Security Assessor (QSA) and is certified as a PCI Level 1 Service Provider. This is the most stringent level of certification available in the payments industry. MICRO™ uses one of PayPal's recommended payments integrations to collect payment information, which is securely transmitted directly to PayPal without having them passing through MICRO™ servers.
To know more about how MICRO™ uses PayPal for security click here.
To know more about how PayPal is certified as a PCI Level 1 Service Provider click here.
All of the application infrastructure for MICRO™ is running on open-source software CS CART, entirely hosted on our servers without any third-party access to the code. CS CART uses hashing algorithms (SHA-256) in password management to strengthen and encrypt sensitive data. It improves and avoids cross-site scripting (XSS) attacks by making the data escape from the client code.
To know more about CS CART Security click here.
All data is stored in certified databases managed on-location by authorized MICRO™ developers, which implement security measures to ensure that the data is fetched and delivered with encryption on both sides. The database is backed up periodically and every transaction and updates are made using File Transfer Protocol with secure channels.
Our extensions and web front-ends are all configured to use the latest TLS version with a valid, signed, domain-specific certificate and a strong set of cryptographic protocols. Our encrypted-by-default philosophy also means that we don't support fall-back to unencrypted communications (e.g. https -> http). Hence when the users visit any webpage in MICRO™, it is SSL Encrypted with private keys enabled for each session.
We classify data according to the type and sensitivity and use that classification to define which systems are authorized to access and store different types of data. The data sensitivity is used in the risk assessment process to determine the appropriate level of security controls. Backup and retention of data is defined as part of this process.
Direct access to databases and backups is limited to MICRO™ developers and executive personnel. Access to sensitive data is limited strictly to people who need it to do their jobs. We review access periodically and offboard people who no longer need access. Each developer has unique credentials and a single-login method is enforced. These databases are only accessible through a MICRO™ controlled Database Console.
MICRO™ employs role-based access controls to servers containing application data. Authorized employees must use individual account and authentication credentials to gain access. MICRO™ controls access to servers and data stores through authentication handled with key-based SSH sessions. We operate on the Principle of Least Privilege, which means access to a system is only granted if absolutely required to serve a legitimate business need. Our employees only have access to data and systems they need to do their job. MICRO™ requires security awareness training for all employees. MICRO™ will ensure that only authorized personnel login and that access is removed in timely fashion.
MICRO™ users must authenticate with an email and password. Password are stored as cryptographic hashes in the database with the data handled by limited number of MICRO™ developers. Each login has lowered session time and hence when a user is inactive in the account, the session is canceled.
MICRO™ has formalized hiring policies and procedures, performance management, and termination practices. Access to company systems is removed as soon as possible once it is no longer needed. MICRO™ conducts comprehensive pre-hire background checks.
Our developers review secure coding standards applicable to the environments, languages, and platforms they are working in. These standards include ensuring access control of data, sanitizing input/output values, and logging violations that could indicate an attack or vulnerability.
Data we receive from government agencies belongs to them, not to MICRO&trade.