OpenText Voltage
OpenText Voltage: Data Security platform. Data encryption, tokenization, data discovery, data masking. Sensitive data protection throughout its lifecycle.

Key Features
- SecureData - data encryption and tokenization
- Data Discovery - finding sensitive data
- SmartCipher - file and folder encryption
- Data Privacy - masking, pseudonymization
- Structured Data Manager - archiving and retention
Table of Contents
What is OpenText Voltage?
Protecting sensitive data has an unglamorous prerequisite that most projects discover late: knowing where it is. Encryption, tokenization and masking are cybersecurity decisions you can only make about data you have found — which is why discovery, not the cipher, is usually the hard part.
OpenText Voltage (formerly Micro Focus Voltage) is a Data Security platform - solutions for protecting sensitive data: encryption, tokenization, discovery, masking. Protects data at rest, in transit, and in use.
Main components:
- SecureData - encryption and tokenization
- Data Discovery & Classification - finding PII/sensitive data
- SmartCipher - file encryption
- Structured Data Manager - database archiving
What problem does it solve?
flowchart LR
subgraph Without Data Security
A[PII data in clear text] --> B[Breach]
B --> C[GDPR fine 4% revenue]
C --> D[Reputation loss]
end
subgraph With Voltage
E[Encrypted data] --> F[Breach]
F --> G[Data useless]
G --> H[No fine]
end
style A fill:#dc2626,stroke:#b91c1c,color:#fff
style B fill:#dc2626,stroke:#b91c1c,color:#fff
style C fill:#dc2626,stroke:#b91c1c,color:#fff
style D fill:#dc2626,stroke:#b91c1c,color:#fff
style E fill:#22c55e,stroke:#16a34a,color:#fff
style F fill:#f59e0b,stroke:#d97706,color:#fff
style G fill:#22c55e,stroke:#16a34a,color:#fff
style H fill:#22c55e,stroke:#16a34a,color:#fff
Common problems:
- Sensitive data (PII, PCI) in databases without encryption
- Unknown where sensitive data is in the organization
- GDPR/PCI DSS requires data protection
- DevOps needs test data without PII
- Legacy apps don’t support native encryption
How does Voltage work?
flowchart TD
A[Sensitive data] --> B{Voltage SecureData}
B --> C[Tokenization]
B --> D[FPE Encryption]
B --> E[Masking]
C --> F[Token: XXXX-1234]
D --> G[Encrypted: same format]
E --> H[Masked: ****-****-****-1234]
F --> I[Secure storage]
G --> I
H --> J[Dev/Test environments]
style A fill:#dc2626,stroke:#b91c1c,color:#fff
style B fill:#f59e0b,stroke:#d97706,color:#fff
style C fill:#22c55e,stroke:#16a34a,color:#fff
style D fill:#22c55e,stroke:#16a34a,color:#fff
style E fill:#22c55e,stroke:#16a34a,color:#fff
Voltage Components
SecureData Enterprise
Tokenization and encryption
- Format-Preserving Encryption
- Tokenization
- Data masking
- Key management
Data Discovery
Finding data
- PII/PCI scanning
- Structured & unstructured
- Classification
- Risk scoring
SmartCipher
File encryption
- Transparent encryption
- File shares, cloud
- Policy-based
- Key recovery
Structured Data Manager
Database archiving
- Data retirement
- Legal hold
- Compliance archiving
- Database optimization
SecureMail
Email encryption
- End-to-end encryption
- Policy-based
- No PKI required
- Mobile support
Payments
PCI tokenization
- Card tokenization
- Point-to-point encryption
- PCI DSS scope reduction
- Payment gateway integration
Format-Preserving Encryption (FPE)
Unique Voltage technology - encryption preserving data format:
| Original | Standard AES | Voltage FPE |
|---|---|---|
| 4111-1111-1111-1111 | xK9#mL2$pQr… | 7823-9012-3456-7890 |
| 123-45-6789 (SSN) | Base64 blob | 987-65-4321 |
| john.smith@company.com | Encrypted blob | abc.defghij@klmno.pq |
FPE benefits:
- Applications don’t require changes (same format)
- Databases maintain structure
- Reports work without modifications
- Legacy apps protected
flowchart LR
A[App: Card 4111...] --> B[Voltage FPE]
B --> C[Encrypted: 7823...]
C --> D[Database]
D --> E[App reads 7823...]
E --> B
B --> F[Decrypted: 4111...]
style A fill:#6366f1,stroke:#4f46e5,color:#fff
style B fill:#f59e0b,stroke:#d97706,color:#fff
style C fill:#22c55e,stroke:#16a34a,color:#fff
style F fill:#22c55e,stroke:#16a34a,color:#fff
Data Discovery Use Case
Finding sensitive data in the organization:
flowchart TD
A[Data Discovery] --> B[Scan databases]
A --> C[Scan file shares]
A --> D[Scan cloud storage]
B --> E[Found PII]
C --> E
D --> E
E --> F[Classification]
F --> G{Sensitivity?}
G -->|High| H[Enforce encryption]
G -->|Medium| I[Alert + review]
G -->|Low| J[Tag + monitor]
style A fill:#6366f1,stroke:#4f46e5,color:#fff
style E fill:#f59e0b,stroke:#d97706,color:#fff
style F fill:#8b5cf6,stroke:#7c3aed,color:#fff
style H fill:#dc2626,stroke:#b91c1c,color:#fff
Detected data types:
- PII: names, addresses, SSN, email
- PCI: card numbers, CVV, expiry
- PHI: medical data (HIPAA)
- Credentials: passwords, API keys
- Custom patterns: any regex
Who is it for?
Voltage MAKES sense when:
- • You process personal data (GDPR, RODO)
- • Payment cards - PCI DSS compliance
- • Legacy apps that don't support encryption
- • DevOps needs realistic test data
- • You don't know where your sensitive data is
Voltage DOESN'T make sense when:
- • Only file encryption - BitLocker may suffice
- • Cloud-native apps with built-in encryption
- • Small scale without compliance requirements
Voltage vs competition
| Aspect | Voltage | Thales | IBM Guardium | Protegrity |
|---|---|---|---|---|
| FPE | Yes (inventor) | Yes | Yes | Yes |
| Tokenization | Yes | Yes | Yes | Yes |
| Data Discovery | Yes | Limited | Yes | Limited |
| File Encryption | SmartCipher | CipherTrust | No | No |
| Email Encryption | SecureMail | No | No | No |
| PCI Focus | Voltage Payments | Yes | Yes | Yes |
Voltage advantage:
- Inventor of Format-Preserving Encryption
- Comprehensive portfolio (FPE + Discovery + Files + Email)
- Voltage Payments for PCI
- Integration with OpenText security stack
Specifications
| Parameter | Value |
|---|---|
| Deployment | On-premises, SaaS, Hybrid |
| Encryption | AES-256, FPE (FF1, FF3-1) |
| Key Management | Built-in, HSM integration |
| Databases | Oracle, SQL Server, DB2, PostgreSQL, MySQL |
| Cloud | AWS, Azure, GCP |
| Compliance | PCI DSS, GDPR, HIPAA, SOX |
FAQ
What is tokenization? Replacing sensitive data with a token (random identifier). Original in secure vault. Token useless without vault.
FPE vs tokenization - which to choose? FPE when you need to preserve format and reversibility. Tokenization when you want to completely separate data from its representation.
Do applications need changes? Not for FPE - format preserved. For tokenization, integration with vault may be needed.
How long does data discovery take? Depends on data volume. Petabytes = days. Can scan incrementally.
What about performance? FPE adds ~1-5% overhead. Voltage offers hardware acceleration.
Does nFlo implement Voltage? Yes. SecureData, Data Discovery deployments, database integrations, PCI tokenization.
Inquire about OpenText Voltage
Contact your product specialist and get a custom quote.

Related Services
Our services supporting the implementation and management of this solution
Active Directory Security Audit
Cybersecurity
We find paths to Domain Admin before attackers do.
CIS Security Audit
Cybersecurity
Harden system configurations to CIS Benchmarks. Close the default settings attackers look for.
Cloud Security Audit and Protection
Cybersecurity
Check AWS/Azure/GCP security before attackers find misconfigurations. CSPM + manual review.
Web Application Penetration Testing
Cybersecurity
One SQL injection = access to entire database. Find vulnerabilities before hackers do.
From Our Knowledge Base
Articles related to this solution
Clean restore point after ransomware: how to check a backup before you restore it
A practical guide to ransomware recovery: how to choose a clean restore point, why the latest backup may be infected, where and what to check before restoring, how to rebuild identity and in what order to return to production — based on CISA, NIST and CERT Polska.
GRC (governance, risk, compliance): how to combine them in one cybersecurity process
A guide to GRC in cybersecurity: the OCEG definition, the difference between governance, risk and compliance, the GOVERN function in NIST CSF 2.0, board obligations under NIS2, the amended Polish Act on the National Cybersecurity System and DORA, a shared register of requirements, risks and controls, and a maturity check for the process.
DNSSEC: what it protects, what it doesn't and how to enable it for a .pl domain
A practical guide to DNSSEC for administrators and CISOs: the chain of trust, protection against forged answers, the limits of that protection (confidentiality, DoS, the registrar account), DoT and DoH, checking a domain, enabling it for .pl through the registrar, choosing an algorithm under RFC 9904, typical outages and NIS2 requirements.
Related Products
Other solutions you might be interested in
Aruba ClearPass
Aruba Networks
Aruba ClearPass: NAC platform with profiling of 70+ thousand device types. Zero Trust access control for users, BYOD, and IoT.
Barracuda CloudGen Firewall
Barracuda Networks
Barracuda CloudGen Firewall: next-gen firewall with SD-WAN. IPS, application control, VPN, threat protection. Appliance, virtual, cloud.
Barracuda Email Protection
Barracuda Networks
Barracuda Email Protection: AI-powered email security against phishing, ransomware, BEC and account takeover. Gateway + API for Microsoft 365 and Google.
Barracuda SecureEdge
Barracuda Networks
Barracuda SecureEdge: SASE platform combining SD-WAN with cloud security. Zero Trust, SWG, CASB, FWaaS. Protection for distributed workforce.
Want to Reduce IT Risk and Costs?
Book a consultation - we respond within 24h
Or download free guide:
E-book: Digital Resilience Strategy 2026