Fortify 24x7 stands behind this storefront. Controls presented, worked, and reconciled entry by entry.Open your recordWrite to an engineer
FinShield Tech
Session 03 / Mailbox and pretext

The message that costs a firm money is the one that reads exactly like the others.

Fraud aimed at a financial practice rarely arrives looking hostile. It arrives as a revised set of instructions from a name the recipient already trusts. These two entries put detection inside the mailbox where that message lands, and put short instruction in front of the people most likely to be asked.

IronscalesMicrosoft 365 and Google WorkspaceAPI, never a gateway
2 entries / mailbox-level API protection / instruction by result
Entries here2
Carried onIronscales
Rate basisMailbox or trained person
DeskAnswered around the clock

Inside the tenant rather than in front

A gateway stands in front of the mail service and inspects traffic passing through it. There is a hole in that arrangement: it never sees what is already resting in a mailbox, and it never sees a message one colleague sends another. Ironscales joins the mail tenant itself over an API, Microsoft 365 and Google Workspace alike, and reads a message once it has arrived. Both holes close.

This is protection living at the mailbox, reached over an API, and explicitly not a gateway. The distinction matters the moment somebody asks what changes about mail routing, because the truthful answer is nothing whatsoever. No rerouting. No new entry in your public naming.

No rerouting, no change to your naming records, and the inspection happens where the message already is.

The half made of people

A convincing pretext gets past a filter by being unremarkable. What remains is the person reading it, and whether anything in their week has taught them to slow down at precisely the point where a payment instruction changes.

Instruction goes out by result rather than to the whole practice on a single afternoon. Somebody who clicks gets a short module that week. Somebody reporting a genuine attempt improves the tenant for everybody else. It is a small loop, and the only part of this session that improves without us touching anything.

Entries in this session

Entry specifications

Billing hands over every figure below at page load. Present while you read; a quantity stands until you alter it.

Fortify-FES+SATEntry

Mailbox Defense with Training

Ironscales attached inside the tenant, instruction alongside

Ironscales reaches into the tenant by API, Microsoft 365 and Google Workspace alike, and reads a message once it has landed. Protection living at the mailbox, reached over an API, and explicitly not a gateway; we decline to blur those two.

  • Detection for impersonation and for account takeover, tuned on your own tenant history.
  • Anything convicted post delivery is withdrawn from every box it reached.
  • Short instruction reaches whoever needs it, not everybody on one afternoon.
Settles onIronscales, attached by API to your mail tenant
NetsOne mailbox, protection and instruction on a single unit
Value dateOpens the moment the tenant grant is accepted
Cleared byFortify 24x7 engineers, assisted by your own reporters
Reconciled byConviction history and instruction completed, person by person
Reading the rateper mailbox
settled monthly, in advance
QTY
Fortify-SATEntry

Phishing Simulation and Training

Ironscales instruction standing alone

For anybody wanting the practice without a mailbox on the protection entry: contractors, seasonal preparers, and whoever reads practice mail from an address you do not host.

  • Simulated messages shaped like the ones this sector genuinely receives.
  • Short modules go out on results, never as an annual sitting for everybody.
  • Completion and click history kept person by person for the program file.
Settles onIronscales instruction, with no mailbox connection required
NetsOne person under instruction, simulations and modules together
Value dateThe opening campaign can run inside enrollment week
Cleared byFortify 24x7 sets the campaigns and reads what comes back
Reconciled byDated completion records, handable across a table
Reading the rateper user
settled monthly, in advance
QTY
Unmatched items

What this session does not settle

Two entries, each with a visible edge. What follows is what they will not do.

  • No filter catches everything. A pretext written by somebody who has read your real correspondence can be indistinguishable from it. This cuts volume and buys attention. It removes nothing from whatever procedure your practice runs before money moves.
  • Not a gateway, and it will not behave as one. Wanting mail held ahead of delivery, or routing altered inside your naming records, is separate work on a separate product.
  • Instruction is not a certificate. Completion records carry dates and export cleanly. They record that a person finished a module. They do not record that the person will never be fooled.
  • An unconnected mailbox is an uncovered mailbox. An address somebody uses personally for practice business, or a second tenant nobody mentioned at scoping, falls wholly outside this session.
  • Archiving is a different requirement. Holding mail for a records obligation is not what happens here. Copies of a mail tenant belong to session 06.
TICK 01

Heads up: card statements show FORTIFY 24X7 - FinShield Tech is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.