Inovai / AI security
What can an attacker find out about you in an hour?
Using public sources, we show what an attacker can learn about you and how they would use it.
3 domains2 without SPF and DMARC, sender can be spoofed
47 people on social networks12 in IT or finance roles, 5 mention internal tools
5 accounts in breachespasswords from third-party services, 2 match your password policy
31 documentsmetadata: author names, software versions, internal paths
Attack scenario
From: “CFO”
Hello, please pay the attached invoice urgently, I’m travelling.
priority 1Targeted phishing of the accounts teamSpoofed domain, names from LinkedIn, style from public emails.
Problem
Domains, leaked passwords and staff profiles are enough for targeted phishing.
What we’ll do
We go through public sources only and build a realistic attack scenario.
Result
A report with priorities: what to fix first.
What you get
Your company through an attacker’s eyes, and the order of fixes.
Findings with evidenceForgotten subdomains, company emails in password leaks, public documents with internal details. Each with a source and a recommendation.
Targeted phishing scenarioWho would get which email, from whom, and why they would trust it. We describe the scenario; we don’t send it.
Fix prioritiesRanked by what would help an attacker most and what can be fixed fastest. Usually passwords and two-factor authentication.
How we proceed
Consent, collection, evaluation, report.
firma.czdomainFirmabrand12 peoplescope
Step 1Consent and scopeWe define domains, brands, people and sources in writing. We don’t start without a signature from an authorised company representative.deviation
Source for every findingTarget: accounts teamScenario: fake invoice
Step 3EvaluationWe combine the findings into a picture through an attacker’s eyes: the weak spot, the most likely target, a plausible attack.Verified by a humanOSINT reportP1Targeted phishing of the accounts teamP2Passwords in breachesokSPF and DMARC
Simulated phishing of employees is a separate activity with separate consent. We delete working data after handing over the report.
Start with one investigation.
What an attacker can find about your company and management in public sources. We start once an authorised company representative has signed.
Will you touch our systems?
No. The investigation touches nothing; it only pieces together what is visible from outside, and it often decides what to test next.
Will you find our people’s passwords?
We find out which company emails appear in known breaches and whether a password was included. We don’t try the passwords and don’t hand them over in full.
Can the investigation harm anyone?
The report shows people as targets, not culprits. We write it so management sees the risk and employees can defend themselves. We process personal data only to the agreed extent and delete it once the report has been handed over.