The most valuable accounts are the least watched
Accounts with full rights over an organisation's servers, databases, switches and firewalls are exactly the accounts attackers look for. Yet in many organisations their passwords live in a spreadsheet, a notebook or a message shared within the team. Outsourced IT providers use the same administrator password for years, passwords known to departing staff are never changed, and when you ask who made a critical change on a server the answer is often “we don't know”.
Privileged access management (PAM) exists to answer that problem: keeping privileged credentials in a central password vault, controlling who reaches which system, when and with whose approval, and recording what was done in a form you can show afterwards.
Why PAM is a discipline of its own
Classic identity management answers “who is this person?”. With privileged access the real questions are:
- Should this person reach this system, right now?
- Do they actually need to know the password, or only to connect?
- What did they do in the session, and how will we show it later?
- If something goes wrong, can we end the session immediately?
These questions are part of daily operations, especially for organisations with outsourced IT, IT teams serving several clients and sectors with audit requirements.
The building blocks of good PAM
1. Grant access without revealing the password
PAM's central principle is simple: users need to connect, not to know the password. When the credential is injected from the vault straight into the connection, the user never sees it, so they cannot write it down, share it or take it with them when they leave. A password generator for strong passwords and rotation reminders for regular changes complete the picture.
2. Scope access and give it an expiry date
“Everyone can reach everything” is the opposite of PAM. Vault entries should be assigned per client, machine group or organisation, and for a limited time. Giving an outside consultant access only to the relevant servers and only for the duration of a project stops forgotten standing permissions piling up.
3. Approval and time restrictions
Access to critical systems should be able to depend on a second person's approval. Add allowed hours and a maximum session length, and an unexpected administrator session opened at midnight becomes an exception that stands out on its own.
4. Session recording and a searchable command log
A recording is both a deterrent and evidence. Screen recording shows what happened in a session visually, while a keystroke and command log lets you answer questions such as “who dropped this table?” or “who created this user?” without watching hours of video. Telling users clearly that the session is being recorded matters for both transparency and deterrence.
5. Live visibility and intervention
Recordings tell you about the past, but sometimes you need to act on what is happening now. Seeing open sessions live, joining a session or disconnecting it is how a suspicious action is stopped before it completes.
6. Cover devices where no agent can be installed
A large share of privileged access goes not to servers but to network devices: switches, firewalls, older Linux systems. Installing software on them is often impossible. If a PAM solution does not cover these targets with the same vault, approval and recording rules, the most critical infrastructure stays in the blind spot.
Common mistakes
| Mistake | Consequence |
|---|---|
| Sharing one administrator password across the team | No action can be traced to an individual. |
| Open-ended access for outside contractors | The contract ends; the access remains. |
| Leaving network devices outside PAM | The most critical infrastructure is managed without records. |
| Keeping video recordings only | Post-incident review takes hours; commands cannot be searched. |
| Forgetting to rotate passwords | Passwords known to former staff stay valid. |
Where to start
PAM projects often set out to cover everything at once and stall halfway. A more realistic path is to move step by step:
- Take an inventory: which privileged accounts exist on which systems, and who knows their passwords today?
- Start with the most critical targets: domain controllers, database servers, firewalls and core switches come first.
- Move passwords into the vault and change them: a password that goes into the vault should stop working for everyone who knew it before.
- Put an end date on outside access: give every outside IT provider and consultant access that expires.
- Review recordings regularly: keeping records is not enough; out-of-hours sessions and unexpected commands should be reviewed periodically.
PAM and KVKK
Knowing who accesses the databases and servers that hold personal data is a natural part of the technical measures expected under KVKK, Türkiye's personal data protection law. Limiting rights to what each role needs, recording access and being able to produce those records when asked lets you give a concrete answer to “who did what, and when?” during a breach investigation.
Password vault and recorded privileged access with Marta Security SAM
Marta Security SAM — Cyber Analysis Centre Management Software, developed by Marta Teknoloji, is a threat detection and threat notification system. Alongside threat monitoring, case management and DLP, the same console offers a password vault and recorded privileged access:
- Browser-based access: RDP to Windows endpoints, SSH and VNC to Linux endpoints, with no extra client software.
- Agentless targets: RDP, SSH, VNC and Telnet to servers, switches, firewalls and Linux hosts where no agent can be installed.
- Password Vault: a per-organisation credential vault; passwords are added to the connection without being shown to the user.
- Time-limited assignment: vault entries are assigned to users per client, group or organisation for a set period, with a password generator and rotation reminders.
- Access rules: access approval, allowed hours, maximum session length and a “this session is being recorded” notice.
- Session recordings: screen recording and keystroke/command log stored securely, with in-browser playback and log search.
- Sessions page: view open RDP, SSH and console sessions live, join them or disconnect them.
- Remote access log: operator, machine, organisation, protocol, duration and status, downloadable as CSV.
Console sign-in can use optional TOTP-based multi-factor authentication, ready-made role templates or a permission matrix. Retention for session recordings is set per organisation. Thanks to its multi-tenant design, IT teams serving several clients can manage each client's vault, users and recordings separately.
You will find every feature of Marta Security SAM on our product page. To walk through your privileged access processes with us and arrange a demo, get in touch.
