OpenText Voltage

What is OpenText Voltage?

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

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 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.