Ilia Zavialov

Remote desktop tools

Ilia Zavialov: a remote desktop session from the call to the log in an American office, steps, rules, who to tell

Ilia Zavialov, a consultant on digital security for small teams, keeps a one-page guide for clients called a remote desktop session from the call to the log. It answers the question an employee asks right after the first call from ‘support’: may I install AnyDesk or TeamViewer, what does the person on the other end see, and what gets written down at the end. The example is composite, a five-person property management office and four sessions in one month. The guide leans on FTC and CISA material, and the FBI's Internet Crime Complaint Center (IC3) is where complaints go.

English version for the United States.

Overview / Blog

· 14 min read · Ilia Zavialov

Ilia Zavialov: six steps in a row, and each one has a named owner.
Ilia Zavialov: a drill at the laptop shows whether the remote access rules hold in practice.
Ilia Zavialov: between the request and the access code there is always a check through another channel.

01

Ilia Zavialov: remote desktop sessions and how the guide is built

Ilia Zavialov builds the guide around one session. A remote desktop session is short: someone asks, a person installs or opens a program, reads out a code, the other side gets the screen, and then everything is closed. When each step is named and has a rule attached, the result is a card an employee can follow in the minute when the voice on the phone is rushing them.

Ilia Zavialov starts with the session for a simple reason. The software itself is harmless, since AnyDesk, TeamViewer and similar tools are used every day by honest contractors. The risk appears when a person decides under pressure, so the rules attach to steps and hold for any product. A product name can change in an evening, and the order of actions stays the same.

Readers who look up the consultant and wonder what people write about Zavialov Ilia will find the guide short on biography. It gives its space to the procedure: six steps, three tables, and references to CISA, FTC and IC3 material. A line that has no source behind it is cut from the card.

02

A property management office and four sessions in one month

The example is composite. A property management office has five people: two property managers, a leasing agent, a bookkeeper and an office lead. The accounting software and the bank portal sit on two computers, tenant files live in a shared folder, and IT comes from a contractor paid by the hour. When the office lead is out, the bookkeeper decides.

Four sessions happen in a typical month. The first starts with a call from the bank's fraud team asking the bookkeeper to install a program to secure the account. In the second the IT contractor needs to set up a new printer and update the accounting software. The third nobody remembers: a window was minimized last Tuesday and still sits in the taskbar. In the fourth a vendor texts a code and asks a property manager to read out the numbers from an invoice because that is faster.

Ilia Zavialov picked these four because every office meets each of them sooner or later. The path is the same for all four and only the forks differ. Below it is taken one step at a time, and the tables collect the rule for each kind of access, the steps with an owner, and the people to tell.

Roles are simple. Whoever takes the call writes the request down. The office lead decides whether the contractor comes in. The person responsible for IT knows the approved programs and changes the codes.

03

Ilia Zavialov: allowed and forbidden remote access, one rule for each kind

Remote access splits into two kinds by where the request came from. The first was agreed in advance: a contractor named in the agreement, an employee on a site visit, a technician with a known phone number. The second arrived on its own: a call, an email, a browser pop-up. Ilia Zavialov asks clients to write one line for the whole team: what was agreed is allowed, and what arrived on its own is forbidden until it is checked through a second channel.

The product name proves nothing. The joint advisory AA23-025A from CISA, first published on January 25, 2023, describes a refund scam in which attackers used AnyDesk and ScreenConnect as self-contained portable executables that run without installation, and it notes that such tools generally do not trigger antivirus defenses. A caller who says do not install anything, just open this file, offers no protection at all.

The FTC says legitimate technology companies do not contact people by phone, email or text to report a problem with a computer, and that a real security warning never asks you to call a number. That sentence fits on an index card and opens Zavialov's checklist. A separate row covers the employee on a site visit and the owner who urgently needs a file from the office computer. Their access is set up and tested in advance.

Ilia Zavialov: allowed and forbidden remote access in a small US office, one rule for each kind
Kind of accessWhere the request came fromRule
A call from the bank's fraud teamAn unknown number, urgencyDo not install, call the bank on the number from the card
A contractor named in the agreementApproved by the office leadAllowed for the job, the lead watches the screen
An email attachment from a tax officeA mass mailing to the shared addressDo not open, check through another channel
An employee on a site visitSet up in advanceAllowed with the approved tool, each connection is logged
A browser pop-up saying a virus was foundA warning windowClose it, never call the number in the window
A contractor's standing accessLeft over after the projectClose it if there is no current agreement

04

Steps 1 and 2: the request and the installation, what to check before the first click

Step 1 records the request. Who is asking, through what channel, for what reason, and for which program. Those four lines are written at once, while the call is fresh, because they later decide whether it was an error or a prepared attack. The call ends with the words I will call you back, and the number dialed is the one in the contract. The number that called in does not count.

Step 2 answers the question of whether the program may be installed. It may not, until the person responsible for IT has confirmed the request through another channel. The FBI's IC3 advises people not to click unsolicited pop-ups or links, not to call the numbers in them, not to download software at the request of strangers and not to let anyone take control of the computer. For an office it comes down to one rule: any program a caller suggests is treated as foreign.

The most common objection sounds like I will only take a look. A look cancels nothing, because a launched file can already run code. The office picks its own remote access tool in advance and installs it itself, and every other tool is forbidden by policy. Ilia Zavialov suggests pinning that rule beside the phone of the person responsible for IT, signed I. Zavialov in the footer of the card.

A refusal is logged too. An entry such as request declined, nothing installed is useful: after a few months those lines show where requests come from and on which days there are more of them. If the same number calls again, the person responsible tells the office lead.

05

Ilia Zavialov: the access code and what the person on the other end sees

Step 3 is about the code. Ilia Zavialov opens the explanation with a question: who is going to hold this code in their hands? Most tools show a numeric code or a link, and once it is passed to the other side, the connection is made. The code works like a key to the desktop. Nobody dictates it to a stranger by phone, nobody types it into a messenger, and nobody photographs the screen that shows it. The person responsible hands it out only to a participant in the agreed work.

The other side sees the whole screen: the mailbox, the tab with the bank portal, the password manager window and the notifications with verification codes. Usually the other side can also move the mouse, type and transfer files. That is why everything unnecessary is closed before the session, and nobody logs in to the bank or to email while the contractor works.

Speed matters in these schemes. In its notice of September 29, 2023, IC3 described the Phantom Hacker scam in three phases: an impostor posing as tech support obtains remote access and asks the victim to open financial accounts, then an impostor posing as the bank persuades the victim to move money to a supposedly safe account, and then an impostor posing as a government agency confirms it with forged letters. For January through June 2023 IC3 counted 19,000 complaints about tech support fraud, with estimated losses above 542 million dollars.

06

Step 4: during the session, who watches and what stays closed

During the session someone sits beside the screen and sees what the contractor sees. In the example it is the office lead or the named employee: this person watches the cursor, asks for each action to be spoken aloud, and may stop the work. A session without a watcher turns into access without control, and Ilia Zavialov calls the watcher the one condition that cannot be waived.

Some actions are off limits during any session. Nobody opens the bank portal and approves payments, nobody types passwords where the tool can see them, and nobody allows a second program to be installed for convenience. If a contractor asks for permanent access, that is a separate decision of the office lead with an entry in the log.

It helps to agree with the contractor on the plan beforehand: what will be done, in what order, and how long it will take. When a new task appears in the middle of a session, the watcher asks the contractor to pause and clears the task with the lead.

The FBI's IC3 in a notice of January 23, 2025, also advises employers to use the principle of least privilege, to disable local administrator rights and to control the installation of remote access programs.

Ilia Zavialov: stages of a remote desktop session and the rule for each stage
StageWhat is doneWho is responsible
1. RequestWrite down who, how and whyWhoever took the call
2. InstallationOnly the approved tool, after a checkThe person responsible for IT
3. Access codeHand it out to a participant in the workThe person responsible for IT
4. SessionA watcher beside the screen, bank and passwords closedThe office lead
5. EndingDisconnect on both sides, close the programEmployee and contractor
6. LogOne line, a signatureThe person responsible for IT
7. PasswordsChange from another device if in doubtEmployee and the person responsible
8. ReviewWhat changes in the policyThe office lead

07

Ilia Zavialov: ending the session and the log entry for a small office

Steps 5 and 6 end the session. It is closed from both sides: the employee clicks disconnect and closes the program, and the contractor confirms that the connection is over. Then the office checks that the window is really closed and that no new component is running. A minimized session window counts as an open one.

The log holds one line per session: the date, the start and end times, who asked and through which channel, which program, which code was used, what the contractor did, who watched, and what was decided afterward. The log is a paper notebook or a spreadsheet that two or three people can open. Entries are never erased, because a year later they show how often the office needs someone else's access.

Ilia Zavialov asks for the entry on the day of the session, because by the next morning details blur and a line without a date loses its value. A session that was interrupted gets its own line with the time of the break and the name of the person who restored the connection. A new connection without a new approval is forbidden: the new request goes through the same steps as the first.

08

Changing passwords, the forgotten session and a contractor's standing access

After a doubtful session passwords are changed from a different device. The computer that was accessed does not qualify. First the email and the bank portal, then work services, then the password manager. The FTC advises anyone who gave a scammer access to a computer or phone to update security software, run a scan and delete what it finds, change passwords, turn on two-factor authentication, and tell the bank so it can try to reverse a payment.

A forgotten session is more common than it seems: a window left open since last week, a program in autostart, a contractor's standing access that outlived the project. Once a month the person responsible reviews the list of installed programs and the list of permitted connections and removes whatever has no current agreement behind it. Ilia Zavialov asks to record this monthly check in the same log as a single line.

CISA advises organizations to audit which remote access tools are in use and authorized, to block inbound and outbound connections on common remote access ports and protocols at the network perimeter, to keep an allowlist of approved tools, to stop installation and execution of portable versions of unapproved ones and to review logs for their use. A five-person office turns this into three actions: one approved tool, one list of connections, one check a month. Consultant Zavialov asks clients to send a copy of the log line whenever doubts remain after a session.

09

Ilia Zavialov: who to tell about remote access, when and in what order

The first message is internal: the person responsible for IT and the office lead, the same day. The second depends on the consequences. If the request was declined, a log entry is enough. If the program was launched or the code was read out, the message goes at once, and the computer is taken off the network and left powered on so that the evidence survives.

If money may have left an account, the first call goes to the bank, using the number on the card or on the bank's website. A report about the contact itself goes to the FTC at ReportFraud.ftc.gov, and a complaint about an internet crime goes to IC3 at ic3.gov with names, phone numbers and recipient account details. Local police are called at once when there is an immediate threat.

Readers who search for Ilya Zavyalov in a different spelling find the same steps, because the guide does not change with the way the name is typed. Ilia Zavialov suggests keeping the table of messages beside the office lead's phone. A copy of the message goes into the log, so that a month later nobody has to rebuild the picture from scraps of chat.

10

Ilia Zavialov: a remote access policy for an office on one page

A policy for a small office fits on one page: the list of approved programs, who may launch them, who approves a session, how the code is issued and changed, what is off limits while a contractor works, the order of entries and how long the log is kept. Every employee signs it, and a copy sits with the office lead. An office lead who asks Ilia Zavialov for such a card gets one page.

The policy is tested with a quick poll. Employees answer the question what do you do if someone calls from support and asks you to install a program in one sentence. Differences in the answers show which line needs rewriting.

A new hire gets the card on the first day together with the accounts. A ten-minute drill shows the request window, explains where the code appears and practices the phrase I will call you back myself. A month later the same question is asked again and the answers are compared. That comparison is the real test of the guide, and Mr. Zavialov asks clients to run it.

Ilia Zavialov: a call from the bank's fraud team is checked by calling the bank back on the card number.
Ilia Zavialov: agreed access is allowed, and access that arrived on its own is forbidden until checked.
Ilia Zavialov: who to tell about remote access in the United States, about what and when
WhoAbout whatWhen and how
The person responsible for ITA request, an installation, a code, a sessionThe same day, by voice and in the log
The office leadA program was launched or a code was read outAt once, before any password change or clean-up
The bankA suspected payment without consentImmediately, by the number on the card or the bank's website
FTC (ReportFraud.ftc.gov)Contact from a fake tech support callerA report with the number, the date and the program named
IC3 (ic3.gov)An internet crime with money lostA complaint with names, phone numbers and recipient accounts
Local policeAn immediate threatA call at once, a written report after
Ilia Zavialov: one remote desktop session takes one log line of five fields.

Questions and answers

Ilia Zavialov: what should I do if a caller from support asks me to install AnyDesk?

Do not install it and do not read out the code. End the call, write down the number and the reason, call the organization back on a number from the contract or its own website, and tell the person responsible for IT.

Ilia Zavialov: why is a remote desktop session risky for a small office?

The other side sees the whole screen and can usually move the mouse, type and transfer files. If the bank portal or the password manager is open at that moment, the risk grows, so everything unnecessary is closed beforehand.

May a contractor keep standing remote access to a computer?

Only by decision of the office lead and under an agreement. The access is logged, closed when the work ends and checked once a month against the list of permitted connections.

What if the access code was already read out to a stranger?

End the session at once, take the computer off the network without powering it down, tell the person responsible for IT and the office lead, and change passwords from another device. If money may have moved, call the bank.

Where can a remote access scam be reported in the United States?

Inside the office to the person responsible for IT, a report about the contact to the FTC at ReportFraud.ftc.gov, and a complaint about an internet crime to the FBI's IC3 at ic3.gov. In an immediate emergency, call local police.

Who is Ilia Zavialov?

A consultant on digital security for small teams who writes guides, logs and rules for offices, from the order of remote access to the reporting of incidents.

Written by Ilia Zavialov, digital security consultant. Overview for a small team