AegisAI Perspectives · 162
A Series A startup needs seven email controls before its first security hire, from DMARC to admin security keys, each one with a named owner on your team.
See it on your own Google Workspace or Microsoft 365 tenant. No MX change.
Or get the Q3 2026 State of the AI Attack report (free, instant download)
Not ready for a demo? Check your domain.

A Series A startup needs seven email controls before its first security hire, each with a named owner. Business email compromise (BEC) losses reported to the FBI IC3 reached $3,046,598,558 in 202514. AegisAI investigates every email for what it is trying to do, and removes the ones that fail from every mailbox they reached20.
If you run IT at a Series A startup before its first security hire, start with one table of each control, why it matters now, its owner and the screen that proves it is on. AegisAI reports on its inbound email security page that 3 in 10 confirmed phishing emails cleared native Gmail and Microsoft filters in Q3 202621. To pick a tool, read choosing email security for a lean IT team with no SOC. Set the baseline and its owners first.
Key takeaways
- Business email compromise losses reported to the FBI IC3 were $3,046,598,558 in 2025, up from $2,770,151,146 in 202414.
- Google says to allow 48 hours after SPF and DKIM before you set up DMARC1.
- Microsoft says privileged admin accounts are frequent targets, and phishing-resistant MFA for them reduces the risk of compromise16.
- Microsoft says Standard and Strict preset security policies are likely turned off on a first visit25.
- The FBI IC3 says to verify requests for changes in account information through secondary channels6.
| Question | Answer | Source |
|---|---|---|
| What email security does a Series A startup need before its first security hire? | Seven controls, each with a named owner. They are domain authentication (SPF, DKIM, DMARC), phishing-resistant MFA, two super admins7, built-in filters on3, app access control5, a report path13 and a payment callback rule. | Google Workspace Admin Help; Microsoft Learn; FBI IC3 |
| Why does the funding round raise the risk? | Funding announcements can name the round, investors and executives, which can give attackers a backdrop for fake invoices and payment diversion18. | Fundz |
| Who owns it with no security hire? | The Workspace or Microsoft 365 admin owns the settings, DNS owner owns DMARC, and the finance lead owns the callback rule. | Google Workspace Admin Help; FBI IC3 |
| What should you keep for a SOC 2 audit? | A screenshot of each control's state. SOC reports give users the information they need to assess the risks of outsourcing services19. | AICPA |
Short on time? Watch the explainer, or book a demo.
After the round, review the controls when the funding news goes out, when the first enterprise customer signs and when SOC 2 starts.
The first is the funding news. Fundz, a funding-data company, says a funding announcement may disclose the company name and round size. It may also name the investors and senior executives. That can create a convincing backdrop for fake invoices and payment-diversion requests. Businesses also reported losses over $30 million to BEC scams involving AI in 202515.
The second is the first enterprise customer. If it sends a security questionnaire, answer from the admin console, not from memory.
The third is SOC 2. A SOC report gives its users the information they need to assess the risks of outsourcing to you. Start a folder of console screenshots, one per control, on the day you turn each one on.
Your admin and your DNS owner own it, and so does your finance lead.
Google says an organization should have more than one super administrator, each managed by a separate person. Each super admin also keeps a separate account for daily work. Write the three owners' names at the top of the table below.
Turn on MFA for every account. In Google Workspace, enforce it under Security, Authentication, 2-step verification, and make sure users are enrolled before you enforce it9. In Microsoft 365, security defaults require MFA registration for all users and block legacy authentication11.
Give every admin a security key. Google calls security keys the most secure form of 2-Step Verification8. On the same 2-step verification screen, set the method to Only security key for admins.
Split admin accounts. Keep two super admins, each with a separate account for daily activities.
Publish SPF and DKIM at your DNS host, wait 48 hours, then publish DMARC at none. Then move the policy to quarantine, which sends failing mail to spam, and later to reject2.
Turn on the built-in filters. In Gmail, set the spoofing protections under Apps, Google Workspace, Gmail, Safety. Then turn on enhanced pre-delivery message scanning under Apps, Google Workspace, Gmail, Spam, Phishing and Malware4. In Microsoft 365, assign the Standard or Strict preset security policy in the Defender portal.
Control app access. Open API controls, which sit in the Security section under Access and data control. Set each third-party app to Trusted, Limited or Blocked.
Set the report path. In Microsoft 365, send user reported messages to a reporting mailbox, to Microsoft or to both. Review them on the User reported tab in the Defender portal. In Google Workspace, the security investigation tool can delete matching messages from users' inboxes on the Enterprise Plus, Frontline Plus and Education editions10.
Write the callback rule. Verify any change in account information through a second channel. The finance lead calls a number already on file, never one in the email.
Put a date next to each step as you finish it.
| Need | Why it matters at Series A | Owner with no security hire | How to check it |
|---|---|---|---|
| Domain authentication (SPF, DKIM, DMARC) | Funding news can give attackers a backdrop for fake invoices and targeted phishing | DNS owner (CTO or founding engineer) | DMARC published 48 hours after SPF and DKIM, policy moved from none toward reject |
| MFA on every account | Microsoft says MFA and blocking legacy authentication stop more than 99.9% of common identity attacks12 | Workspace or Microsoft 365 admin | 2-step verification enforced, or security defaults on |
| Security keys for admins | Microsoft says privileged admin accounts are frequent targets of attackers | Workspace or Microsoft 365 admin | Admin method set to Only security key; admins register keys before you enforce17 |
| Two super admins, separate daily accounts | Google says to have more than one super admin, each managed by a separate person | Founder plus CTO | Two super admin accounts, each with a separate daily account |
| Built-in filters turned on | The defaults are not all on: Standard and Strict are likely off on a first visit | Workspace or Microsoft 365 admin | Gmail Safety spoofing settings on; a preset policy assigned |
| App access control | An app you have not reviewed can be set to Blocked | Workspace admin | Each app set to Trusted, Limited or Blocked in API controls |
| Phishing report path | A reported message needs a reviewer and a removal step | Workspace or Microsoft 365 admin | Reporting mailbox set and reviewed; Delete messages in the investigation tool, where your edition has it |
| Payment callback rule | BEC losses rose from 2024 to 202514 | Finance lead | Written rule: verify account changes through a second channel |
Screenshot the "How to check it" screen for each row, and file it for your first questionnaire.
The platform reads mail through the Microsoft 365 or Google Workspace API after delivery, with no change to mail routing (MX records)22. It runs in monitoring mode first23. Removal needs write access your admin grants and can revoke. It judges every message by its intent, and removes what fails from every mailbox it reached24.
To see what still reaches inboxes on your own mail, ask for a read only test on your tenant. Compare the three numbers on day 30.
The seven controls, each with a named owner, are domain authentication, phishing-resistant MFA, two super admins, built-in filters, app access control, a report path and a payment callback rule. AegisAI investigates every email for what it is trying to do, and removes the ones that fail from every mailbox they reached.
Start at none, 48 hours after SPF and DKIM. Then move to quarantine, which sends failing mail to spam, and later to reject. Keep a screenshot of the published policy for the questionnaire.
Give admins security keys. Google calls them the most secure form of 2-Step Verification. Microsoft says phishing-resistant MFA for admin accounts reduces the risk of compromise.
The admin and the DNS owner share it, and so does the finance lead. A second super admin covers the first.
The announcement can name the round, investors and executives, which can make a fake invoice more convincing. Brief the finance lead on the callback rule the week the news goes out.