Skip to content
Strategia Informatica
Menu
Contour lines of the terrain between Arzignano, Montecchio Maggiore, Vicenza and the Berici Hills, every 25 metresMontecchio MaggioreVicenzaColli Berici

From cable to data.

Networks, data centres, security, telephony: we design them, keep them in order and, when something breaks or comes under attack, we find the cause and get the service back on its feet. And we build platforms that turn real data, from satellites to the corporate network, into information you can act on.

See our expertise Read the examples

Montecchio Maggiore (Vicenza, Italy), 45°30′ N 11°25′ E The contour lines are real: Copernicus GLO-30 terrain, one every 25 metres. How the map is made

What we can do

Eight areas, each with its capabilities explained, the technologies we use and, where they can be told, examples of work we have done. We only talk about things we have actually done.

Some of our work, without names

We do not name our clients: we describe the problem, what we did and where we got to. Each example states whether the work is in production, delivered, in progress or still a study.

  1. Networks Industrial group In production

    An IPS signature that isolated a server every hour

    The problem
    A server kept losing its connection to the domain at regular intervals, with no obvious trace in the firewall’s traffic logs.
    What we did
    An intrusion prevention signature fired on ONVIF traffic to two cameras, and its block action dropped all of the server’s traffic, 3,700 packets per second; the block renewed itself every time it expired. We created the exception through the APIs of the cloud management system.
    Result
    The server is stable. An automatic check now reads the block tables of five firewall clusters every 3 minutes and sends an alert with an unblock button.
  2. Data centre and backup Services company Delivered

    Ten terabytes from an unreadable volume, verified byte by byte

    The problem
    A 16 TiB ReFS backup repository had become unreadable; it looked like a disk failure.
    What we did
    The “I/O errors” were the underlying storage running out of space; the disks were healthy. We made a full copy to another node (15.6 TB, verified). On a clone we discovered that Windows Server 2025 upgrades the volume irreversibly even without mounting it: on the original, that would have made the only tool able to read it useless. We carried out the extraction on the clone.
    Result
    1,479 files and 10.08 TB extracted with byte-by-byte verification in about 3.5 days instead of the estimated 20; Microsoft 365 backup databases repaired, backups running again, residual damage below 1.6%.
  3. Security and incidents Industrial company Delivered

    Diverted bank transfers: the breached mailbox was not the client's

    The problem
    The company had made several transfers to fraudulent bank details and feared that its own email had been breached.
    What we did
    We analysed the access logs of the internal mailboxes: no anomalous access, no hidden forwarding rules. By cross-checking the message headers we proved that the compromised mailbox was the supplier’s; the counterfeit domain came to light when we computed the distance between the names.
    Result
    Forensic report with a full timeline, indicators and actions: recall of the transfers, blocking of the lookalike domain, verification of the bank details through an independent channel, a mailbox audit and a rule against spoofing of suppliers’ domains.
  4. Telephony and contact centres Contact centre in the distribution sector Delivered

    Two hundred and thirty “suspected dropped calls” a day, none due to the network

    The problem
    An indicator counted about 230 suspected dropped calls a day, 4.9% of the calls handled, and the network was thought to be the cause.
    What we did
    We reconstructed 147 cases one by one: all the repeat calls were new calls and none was a network drop. The causes were mainly three behaviours at the workstation: a microphone with no signal, hold pressed before the call connected, a double click on answer/hang-up.
    Result
    Measurements and safeguards added to the bar, to be enabled after a measurement period.
  5. IoT and embedded Industrial plant Delivered

    An HMI stuck after a blackout, because of a switched-off PC

    The problem
    After a blackout the HMI froze at every start-up; about ten restarts had not helped.
    What we did
    We analysed about 21,000 diagnostic records with a script and documented the exclusion of the other causes: two byte-for-byte identical copies of the project, all PLCs reachable, licences and databases in order. The cause: a PC hosting a server of the distributed system had stayed switched off.
    Result
    Once the PC was switched back on, the HMI started up again. We delivered the incident report, the system fact sheet, the runbook and a checklist for restarts after a blackout.
  6. AI and automation Internal use, hardware purchasing In production

    A quote from eight portals in 40-70 seconds

    The problem
    For a quote we had to open the distributors’ B2B portals one by one, sign in again where sessions had expired and compare prices and availability by hand.
    What we did
    One command queries eight portals, signs in again where sessions have expired and returns net price, list price, availability, promotions and variants, including the actual seller in marketplace offers.
    Result
    Response in 40-70 seconds; automatic sign-in tested on 7 portals. A first version based on a multimodal model that read the pages was replaced by deterministic scripts, which are faster and more predictable.

All examples (112)

How we work

These are habits more than rules: they show in every job, from configuring a firewall to analysing an incident.

  • Measure first, then state

    Every conclusion rests on data: a log, a measurement, a test that can be repeated. When something is estimated or inferred, we say so.

  • Read-only, until something else is needed

    Investigations, checks and inventories change nothing. A system is touched only when it has to be, with a plan.

  • The way back before the change

    A copy of the configuration, a scheduled automatic rollback, the previous version ready: before changing anything we know how to go back.

  • A green dashboard is not enough

    We check the real effect: the latest data received, the service that actually answers, the protection that is actually on.

  • Real data only

    In the platforms we build, every number traces back to a real source. Whatever is modelled or inferred is declared as such.

  • A minimal footprint towards the outside

    Expose as little as possible, with no versions or product names. This site too is made of static pages only.

How we work, in full

One point of contact, from the first visit to the final check

Strategia Informatica is the sole proprietorship of Roberto Dal Brun, active since 2003 in Montecchio Maggiore, in the province of Vicenza, Italy. Whoever calls us has a single point of contact who follows the work from the first visit to the final check. When a project requires it, we work with trusted collaborators and with other companies, each doing their part.

Who we are and how we work with clients

Company name
Strategia Informatica di Dal Brun Roberto
Legal form
Sole proprietorship, active since 2003
Registered office
Via Quasimodo 28, 36075 Montecchio Maggiore (VI, Italy)
VAT number
03088950245
Business register (REA)
VI-298662
Activity
62.10.00, computer programming (ATECO 2025)
Certified email (PEC)
roberto.dalbrun@pecprofessionisti.com

Tell us about the problem

A network to put back in order, an incident to handle, data to make sense of: the first conversation is about understanding whether and how we can help.

Send an email Call +39 328 277 9187