Meridian security
Your data stays in your network. Every action leaves a trail.
Meridian, Hexabin Infotech's product for mainframe operations, runs inside your network, on premises or in your private cloud, and sends nothing to Hexabin. Four roles per client decide who can act, and every action is recorded with its evidence.
Example data from a lab estate.
Your data
Inside your network, and nowhere else.
Meridian is installed with your team, inside your network. What it reads and what it records stay there.
- Where it runs
- Inside your network, on premises or in your private cloud. One install serves your whole company: every client and every LPAR.
- What leaves your network
- Nothing. Nothing is sent to Hexabin, and Hexabin does not host your data.
- What is kept
- The record of what Meridian saw and did stays inside your network, where you can back it up and inspect it. How long it is kept is yours to set.
- Access on the mainframe
- A light footprint, under IDs you own, with the access your security product grants and nothing more.
- Each client on its own
- Every client has its own LPARs, people, roles and rules, and every screen says which client you are looking at.
Who can do what
Four roles, granted per client.
Actions on a client's systems are open to that client's team only. A client's own managers can be given their reports and their audit trail without seeing anyone else's.
Operator
Works the console, answers WTORs and confirms actions from cards, with the batch line always in view.
SME
Defines the named batches, their deadlines, conditions and breach procedures, and draws the flows that handle routine situations.
Manager
Approves batch definitions, chooses how much Meridian may do on its own, and reads attainment and prediction accuracy by month.
Admin
Grants roles, connects the scheduler and the ticket tool, and receives Meridian's alarms about its own health.
Approvals and four-eyes, per client.
Switch them on for the clients whose rules ask for them, so a second person confirms before an action is sent. They are off by default, because operators are trusted.
Autonomy is earned.
Meridian starts by proposing. For each kind of situation and each client you choose propose only, do and tell, or do quietly, and move it back any time. An action taken on its own is recorded like a clicked one.
Audit
Every action recorded with its evidence.
Every reply, command, scheduler action, flow run and ticket write-back is recorded with what Meridian saw, who confirmed it, the time and what came back.
- The evidence comes first: the console lines and the scheduler state that led to the action.
- Actions Meridian takes on its own are recorded exactly like clicked ones.
- Exportable, for your clients and your auditors.
Protection
Encrypted, watched, and checked before release.
How Meridian protects its connections and the credentials it holds, how it watches its own health, and how releases are checked.
Encrypted in transit
Every connection Meridian uses is encrypted with TLS, from your people's browsers to your scheduler and your ticket tool.
Credentials never on a screen
The credentials Meridian uses for your scheduler and ticket tool are stored with restricted access and never shown on a screen.
It watches itself
When something Meridian depends on stops working, such as an LPAR going quiet, it raises an alarm on a channel of its own, apart from your alerts.
Checked before they go live
Every release is checked before it goes live and can be rolled back. Our engineers upgrade Meridian with your team, and you see every step.
Security reviews
Send us your questionnaire.
Your security team will have its own questions. Send them to us and we will answer them.
Questions
Questions about security.
The answers a security review asks for first. Send us your questionnaire for the rest, or write to hello@hexab.in.
How an engagement runsDoes any of our data leave our network?
No. Meridian runs inside your network and keeps what it records there, where you can back it up and inspect it. Nothing is sent to Hexabin, and Hexabin does not host your data.
What authority does Meridian have on the mainframe?
Only what you grant. Meridian works under IDs you own, with access defined by your own security product, and it changes nothing unless a person confirms the action or a flow you approved runs.
Who can act on a client's systems?
That client's team only. Four roles, operator, SME, manager and admin, are granted per client. Approvals and four-eyes can be switched on for the clients that want them.
What is in the audit trail?
Every reply, command, scheduler action, flow run and ticket write-back, with the evidence Meridian saw, the person who confirmed it, the time and the outcome. It is exportable.
How are connections and credentials protected?
Every connection Meridian uses is encrypted with TLS, including your people's browsers, the scheduler and the ticket tool. The credentials it uses are stored with restricted access and never shown on a screen.
What happens when something Meridian depends on stops working?
It tells you. Meridian watches its own health and raises an alarm on a channel of its own, apart from your alerts, so you know when Meridian itself needs attention.
Can a release be rolled back?
Yes. Every release is checked before it goes live and can be rolled back. Our engineers upgrade Meridian with your team, inside your network, and you see every step.
Can we send you a security questionnaire?
Yes. Send it to hello@hexab.in and we will answer it.
Bring your security team to the demo.
Forty-five minutes on a live lab estate. Ask where data lives, who can act and what is recorded, and see the audit trail for yourself.