Connect
Bring agreed information sources into scope so your team can examine content where it lives. Connections depend on supported repositories, versions, permissions and configuration.
Data security platform
A data security platform for better information decisions
Find sensitive information. Understand what needs attention. Decide what to protect, retain or review for disposal.
When information is scattered across file shares and business systems, it is difficult to explain what you hold or which content still has value. WyldLynx helps you turn that uncertainty into practical action with data discovery, classification and information governance.
What is a data security platform?
A data security platform brings together capabilities to discover information, classify its sensitivity, assess risk and support protective action across connected systems. It helps teams understand where attention is needed and organise the work that follows.
For records and information managers, that means better evidence for decisions about retention, sensitive content, migration and appropriate use.
WyldLynx works with OpenText Voltage Data Security Platform (DSP), connecting its discovery and governance capabilities with your information requirements. You may also know its discovery and risk capabilities as Core Data Discovery & Risk Insights (CDDRI) or Voltage Fusion. Product components, supported sources and deployment requirements need to be confirmed for your environment.
Connect, analyse and manage your information
Move from understanding your information to deciding what should happen next, with a clear scope and people responsible for the decisions.
Analyse
Identify potentially sensitive information and risk findings, then prioritise what needs attention. Use the findings to focus review on the collections and issues that matter to your organisation.
Manage
Turn reviewed findings into authorised actions. Confirm retention requirements, holds, exceptions and permissions before changes, including any approved disposal, with accountable owners and recorded decisions.
When could your organisation benefit?
Start with a question you need to answer:
- Where is sensitive information stored outside our governed repositories?
- Which old files still have business or records value?
- What should we review before moving information into Content Manager?
- Which sources are suitable for a proposed AI use case?
A discovery project gives these questions a defined scope. For example, you might examine a shared drive before a migration, review a collection containing personal information or assess the source documents for an internal AI assistant.
Choose an outcome you can evaluate, such as a reviewed migration set or a prioritised list of sensitive-content issues with named owners.
Turn findings into decisions people can act on
Discovery and classification can identify potentially sensitive content and help organise files for review. Information owners then bring the business context: why something exists, whether it remains useful and which obligations apply.
Depending on the selected components, supported versions and source configuration, actions can include masking sensitive information, preserving content on hold, exporting files or carrying out approved disposal.
For an ageing file share, this could mean separating material to retain, content needing protection and files that warrant disposal review. Duplicate or old content still needs a records decision. Check retention requirements, holds and exceptions before approving removal.
Agree who reviews findings, who authorises changes and how decisions will be recorded. Test the proposed actions on a manageable collection before applying them more widely.
Queensland Museum: finding value and risk in existing information
Queensland Museum worked with WyldLynx and OpenText to understand a large collection of existing files. A 30-day proof of value assessed 500 GB of data. The published case found that 11% of assessed files were duplicates and 38% were identified as obsolete.
The work also connected discovery with records management. With tooling support from WyldLynx, qualifying files were moved into OpenText Content Manager, with masking of sensitive information in the described workflow.
It shows how discovery findings can lead to practical information-management changes. The results reflect that project’s scope and data.
Connect discovery with Content Manager
OpenText Content Manager manages records through classification, metadata, access and lifecycle controls. Discovery helps you examine information that may need those controls, as well as analyse supported Content Manager datasets.
Supported integration can process Content Manager content and send selected information to Content Manager targets. The useful design question is what should move, under which rules and with what context.
Before migration, agree the destination, record types, metadata, access and retention requirements. Test sensitive-content handling and check the results with the people responsible for the records. Integration depends on supported versions, permissions and configuration.
Give your AI programme a clearer starting point
Before an AI tool uses a collection, understand what is in it and whether it is appropriate for that task.
Discovery and classification can help identify sensitive material, duplicate content and sources requiring review. Your team can then decide what to include, restrict, update or exclude.
For an internal policy assistant, that means checking which policies are approved and current, who may use them and whether supporting files contain information the assistant should not expose. These decisions help define a controlled pilot. Readiness also depends on access controls, permitted use and testing the AI system’s outputs.
Start with one collection and a clear purpose
Agree the question
Choose a repository, business process or information collection. Identify its owner and the outcome you need, whether that is a migration decision, sensitive-data review or better evidence for an AI pilot.
Confirm the approach
Review the supported connection, deployment, processing location, permissions and review responsibilities. Agree what will be examined and how success will be assessed before the work begins.
Plan the next actions
Depending on the agreed engagement, outputs may include a findings summary, reviewed content groups and a prioritised action plan. Implementation, integration and training can then be scoped around the changes you choose.
Common questions
How does this relate to DSPM?
Data security posture management (DSPM) is the ongoing work of understanding and reducing exposure around sensitive data. A data security platform can provide capabilities to support that work, including discovery, assessment and action. The scope varies between products.
Do we need to scan everything first?
No. A defined collection can help test the approach and understand the review effort before you expand. The right scope depends on the question, source systems and risks involved.
Can the platform decide what we are allowed to delete?
It can help identify and organise candidates. Disposal still needs applicable retention rules, holds, exceptions and authorised decisions built into the process.
Will a data security platform make us compliant?
It can support information controls and evidence. Meeting your obligations also depends on the requirements, configuration, responsibilities and ongoing practices in your organisation.
Bring us the information question you need to answer
Tell us where the information lives, what is difficult to understand and what you want to change. We can help define a useful starting scope and assess how OpenText DSP fits.