Skip to content
Temyro

A Temyro example website. Sentinel Grid is a fictional company; the texts, prices and photos are for demonstration.

Sentinel Grid

Audits · protection · monitoring · incident response

Security that is verified, not assumed.

Sentinel Grid assesses, protects and monitors the infrastructure of companies that depend on their systems. We work with evidence: every finding comes with reproduction steps, an impact-based severity and a remediation plan.

Request an assessment See the services
Illustration · no live threats

Services

Four services, one discipline.

Each service has three tabs: what we do, how it works and what you receive. Open them to see concretely how we work, before any proposal.

Security audit

We check infrastructure, applications and configurations against recognised checklists and through manual testing. We do not stop at a scanner: every reported vulnerability is confirmed by an engineer, with reproduction steps.

Infrastructure protection

We configure and harden what you already have: firewall, network segmentation, remote access, multi-factor authentication, backups. We do not sell equipment; we recommend only what is genuinely missing.

Monitoring

We collect the logs of critical systems and analyse them against rules we define together. Alerts reach people, with context and verification steps, not an ignored mailbox.

Incident response

When something has already happened, we contain, investigate and restore, in that order. We preserve evidence for any legal and notification obligations.

Illustrative diagram

Where we look in an infrastructure.

The layers we assess and monitor, in a diagram typical of a mid-sized company. It is not the map of a real network and shows no traffic or threats.

Press a layer to highlight it in the diagram; press again to reset.

Perimeter Internal network Monitoring Internet Firewall VPN Web server File server Workstations Logs Monitoring team

Scroll the diagram horizontally. Illustrative diagram, no real traffic.

Security operations centre with large screens showing network maps and charts, in blue light

Monitoring

People behind the screens.

A monitoring system produces alerts; an engineer decides whether they matter. We verify every alert before calling you, so that monitoring never becomes a source of noise.

  • Take-over within the windows agreed by contract
  • Verification and context before escalation
  • Monthly report of what happened and what we changed

How an audit works

Five stages, with evidence at each.

An audit is not an auto-generated list. Each stage below has a written result that you receive and can verify.

  1. 1

    Scope and rules

    We define what we test, when and how; all in writing, with contact persons on both sides.

  2. 2

    Inventory and scanning

    We discover exposed systems and run scans in agreed windows, without affecting production.

  3. 3

    Manual verification

    We confirm every finding; what we cannot reproduce does not go into the report.

  4. 4

    Report and prioritisation

    Severity by impact; a remediation plan with order, owners and deadlines.

  5. 5

    Re-test

    After the fixes, we test the closed items again and update the report.

Case studies

Two examples of engagement.

Demonstration case studies, written for this example website: they describe no real clients and contain no figures presented as results.

Demonstration example

Audit for a distribution company

Context
A company with a warehouse, an online store and a few dozen workstations; sales agents connect remotely.
Findings
  • Remote access service exposed directly to the internet, without multi-factor authentication
  • Backups kept on the same server as the data
  • Default passwords on two network devices
Measures
  • Remote access only through VPN, with multi-factor authentication
  • Separate backups, tested through restoration
  • Password changes and an up-to-date equipment inventory
What followed
The critical findings were closed and re-tested; monitoring was switched on for the exposed servers.

Demonstration example

Response to a phishing incident

Context
An employee entered their credentials on a fake page; the account was used to send e-mails to partners.
Findings
  • A forwarding rule added to the compromised mailbox
  • No multi-factor authentication on e-mail
  • Access logs kept too briefly for a complete analysis
Measures
  • Account isolation and removal of the rule
  • Multi-factor authentication for all users
  • Logs kept for twelve months and an alert on new forwarding rules
What followed
Partners were informed with a clear message; the company adopted a written response plan for the future.

Assessment request

Tell us what you protect.

We reply within two working days with a proposed scope and an estimate. Do not send passwords or access details through this form.

For an incident in progress, a real website would show an emergency phone number here; this is an example.

contact@example.com · +40 7xx xxx xxx (demo details)

You have just seen an example website built by Temyro. Sentinel Grid does not exist; everything above is a demonstration. A website like this is made for your business, with its own texts, photos and colours.