In our Ericsson charging environment, my main use case for Enigma Vault handles large volumes of sensitive telecom information such as subscriber personal data, different IMSI and MSISDN addresses, billing information, CDRs, network logs, and SIM related information. Enigma Vault can tokenize or encrypt all sensitive information before it is stored in databases, particularly the PostgreSQL database we use. The data is generally shared with third party systems or used in analytics platforms. The biggest advantage is that even if databases or logs are exposed, attackers only see tokens instead of real customer data. Our organization's key use cases include protecting customer PII data, securing the telecom billing system, and enabling secure data sharing. Cloud security is one of the most important points here. Centralized key management, where encryption keys are managed securely across multiple applications and telecom platforms, is one of the key roles played by Enigma Vault. Regarding daily workflow, the following workflows are encountered in day to day operations. When a customer calls support regarding a billing issue, the CRM application retrieves the customer data. Sensitive fields such as MSISDN and IMSI or payment related data remain tokenized and masked. Customer support agents can only see partially masked values such as 9XXXXX, and instead of the full mobile number, they only see XX digits. Only authorized systems and privileged users can de-tokenize the original value when it is required. Another daily example is our analysis of telecom traffic and customer usage patterns at Ericsson. Instead of exposing real subscriber identities, Enigma Vault provides tokenized data. Analysts can still perform reporting and trend analysis without accessing customer PII. We can extract all that data without touching production. We also use Enigma Vault in cloud environments in container based NTP. Before sending logs or telecom data sets to cloud storage or SIEM tools, sensitive information is encrypted and tokenized through Enigma Vault.
I have been using Enigma Vault for two years. We use Enigma Vault for securely handling sensitive data in our application. Whenever we need to store the data of candidates and enterprises, mostly for the enterprises side, we store it in Enigma Vault. The main use case is to tokenize and encrypt sensitive data, such as the card details of enterprise users, so that the application never stores or processes raw data, ensuring security and compliance. For a specific example, whenever an enterprise user gets added to the application and wants to add 100 or more candidates, they have to pay some minimum amount. For payments, the user will add card details on the front end, but the back end will not store it directly. Instead, it will store it to Enigma Vault. Enigma Vault will perform the encryption of the card data and store it there, then return a token. My database only stores the token, not the actual card number. This approach is especially useful in microservices architecture where multiple services can safely use tokens instead of sharing sensitive data. My system never stores the raw card data, but even if my database is hacked, it will only contain the token. An attacker will only get the useless token. We have reduced our PCI DSS scope significantly.
Unified Endpoint Management offers a centralized platform to manage, secure, and deploy all endpoint devices in an organization. It integrates management across PCs, mobile devices, and IoT, enhancing security and productivity. Enterprise organizations can leverage UEM to streamline IT operations, ensuring all devices are monitored and updated uniformly. With comprehensive visibility into endpoints, administrators can reduce risks associated with unpatched or non-compliant devices. It...
In our Ericsson charging environment, my main use case for Enigma Vault handles large volumes of sensitive telecom information such as subscriber personal data, different IMSI and MSISDN addresses, billing information, CDRs, network logs, and SIM related information. Enigma Vault can tokenize or encrypt all sensitive information before it is stored in databases, particularly the PostgreSQL database we use. The data is generally shared with third party systems or used in analytics platforms. The biggest advantage is that even if databases or logs are exposed, attackers only see tokens instead of real customer data. Our organization's key use cases include protecting customer PII data, securing the telecom billing system, and enabling secure data sharing. Cloud security is one of the most important points here. Centralized key management, where encryption keys are managed securely across multiple applications and telecom platforms, is one of the key roles played by Enigma Vault. Regarding daily workflow, the following workflows are encountered in day to day operations. When a customer calls support regarding a billing issue, the CRM application retrieves the customer data. Sensitive fields such as MSISDN and IMSI or payment related data remain tokenized and masked. Customer support agents can only see partially masked values such as 9XXXXX, and instead of the full mobile number, they only see XX digits. Only authorized systems and privileged users can de-tokenize the original value when it is required. Another daily example is our analysis of telecom traffic and customer usage patterns at Ericsson. Instead of exposing real subscriber identities, Enigma Vault provides tokenized data. Analysts can still perform reporting and trend analysis without accessing customer PII. We can extract all that data without touching production. We also use Enigma Vault in cloud environments in container based NTP. Before sending logs or telecom data sets to cloud storage or SIEM tools, sensitive information is encrypted and tokenized through Enigma Vault.
I have been using Enigma Vault for two years. We use Enigma Vault for securely handling sensitive data in our application. Whenever we need to store the data of candidates and enterprises, mostly for the enterprises side, we store it in Enigma Vault. The main use case is to tokenize and encrypt sensitive data, such as the card details of enterprise users, so that the application never stores or processes raw data, ensuring security and compliance. For a specific example, whenever an enterprise user gets added to the application and wants to add 100 or more candidates, they have to pay some minimum amount. For payments, the user will add card details on the front end, but the back end will not store it directly. Instead, it will store it to Enigma Vault. Enigma Vault will perform the encryption of the card data and store it there, then return a token. My database only stores the token, not the actual card number. This approach is especially useful in microservices architecture where multiple services can safely use tokens instead of sharing sensitive data. My system never stores the raw card data, but even if my database is hacked, it will only contain the token. An attacker will only get the useless token. We have reduced our PCI DSS scope significantly.
I use the solution to collect card data and forward it to a third-party payment processor.