How to check your company's security posture from the outside

CyberRank Research
You can check your company's security posture by reviewing what anyone on the internet can already see: your encryption and certificates, email authentication, exposed services, privacy notices, and whether your domain or staff credentials appear in breach data. Customers increasingly run the same outside-in check before they sign or renew a contract, so it pays to see the result first and fix it on your own timeline. CyberRank's free Cybersecurity & Privacy Rating runs this kind of non-invasive check from a website URL and combines the results into one grade.
TL;DR
- An outside-in posture check looks only at public signals and needs no access to your systems.
- Five areas matter most: encryption, email authentication, exposed services, privacy notices, and breach or credential exposure.
- Customers covered by NIS2, DORA or ISO/IEC 27001 supplier controls are expected to assess suppliers, and many start from these signals.
- Fix findings by priority, re-check, and keep evidence of what changed.
- CyberRank's free rating checks privacy-law indicators, encryption and security configuration, and darknet and breach exposure, then gives one combined grade.
What is an external security posture check?
An external security posture check is an assessment of the security and privacy signals your organisation exposes to the internet, carried out without logging in or touching internal systems.
It answers one question: what would an attacker, a customer or an auditor learn about you from the outside? The same approach underpins most security ratings, as explained in our glossary entry on security ratings. The method itself is explained in detail in our article about outside-in security assessments.
| Area | What is observed | Why it matters | How CyberRank helps |
|---|---|---|---|
| Encryption | What is observedTLS versions, certificates, cipher configuration | Why it mattersWeak or expired encryption exposes data in transit | How CyberRank helpsChecks TLS/SSL configuration and certificates |
| Email authentication | What is observedSPF, DKIM and DMARC records | Why it mattersMissing records make your domain easier to spoof in phishing | How CyberRank helpsChecks email authentication and security headers |
| Exposed services | What is observedOpen services, admin pages, outdated software | Why it mattersEach exposed service is a possible entry point | How CyberRank helpsFlags exposed services and known weaknesses |
| Privacy notices | What is observedPrivacy policy, cookie consent, data subject rights, transfer signals | Why it mattersRegulators and customers read these first | How CyberRank helpsChecks public privacy indicators against UU PDP and similar regimes |
| Breach and credential exposure | What is observedDomain mentions in breach data, leaked credentials, infostealer and paste-site exposure | Why it mattersLeaked passwords are a common route to account takeover | How CyberRank helpsChecks breach corpora and darknet sources linked to your domain |
Start with what others see first
Start with these five areas, because they are what others see first. How CyberRank helps: the free rating scores each area independently from public, non-invasive signals, then combines them into a single CyberRank grade. You can run the free Cybersecurity & Privacy Rating on your own website without registering.
Why should you check your own posture before customers do?
Supplier risk is now a routine part of how customers judge you, and a customer's first impression of your security may come from a rating rather than a conversation.
Verizon's 2025 Data Breach Investigations Report found third-party involvement in 30% of the breaches it analysed, double the previous year's 15%. Buyers have responded by checking suppliers more often and earlier in procurement. Regulation pushes in the same direction.
| Framework | What it asks of your customer | What it means for you as a supplier | How CyberRank helps |
|---|---|---|---|
| NIS2, Article 21(2)(d) | What it asks of your customerAddress supply chain security, including the security of relationships with direct suppliers | What it means for you as a supplierExpect security questions and outside-in checks during onboarding | How CyberRank helpsShows the external signals a customer's check relies on |
| DORA, Article 28 | What it asks of your customerManage ICT third-party risk as part of the ICT risk management framework | What it means for you as a supplierFinancial-sector customers in the EU will assess and monitor you | How CyberRank helpsShows the external signals a customer's check relies on |
| ISO/IEC 27001:2022, controls 5.19–5.22 | What it asks of your customerManage information security in supplier relationships and monitor supplier services | What it means for you as a supplierCertified customers need evidence about your posture | How CyberRank helpsGives a dated rating you can share as evidence |
| Indonesia: UU PDP and OJK outsourcing rules | What it asks of your customerProtect personal data processed by others and manage outsourcing risk | What it means for you as a supplierIndonesian banks and data controllers will review your privacy and security posture | How CyberRank helpsChecks privacy indicators against UU PDP |
Where to read more
If you sell into the EU, the requirements are summarised in our page on NIS2 supply chain security. For Indonesian customers, see our overviews of UU PDP and OJK outsourcing rules. As CyberRank's guide to the difference between a Rating A and a Rating B notes, some tenders set a minimum rating.
How CyberRank helps: checking yourself shows you the same kind of external signals a customer's assessment would rely on, before a deal depends on them.
What does an outside-in check look at?
An outside-in check groups its findings into three families: security, privacy and exposure signals. Each one maps to a different team in your organisation, which matters when you assign fixes.
How CyberRank helps: the free rating covers all three families below in one run, including the post-quantum readiness signal (Beta).
Security signals
Each of the checks below is explained in our guide to what an external security scan checks.
- Encryption in transit. TLS 1.2 should be the minimum, with TLS 1.3 supported. NIST's SP 800-52 Rev. 2 required US government TLS servers to support TLS 1.3 by 1 January 2024, a useful benchmark for everyone else.
- Email authentication. SPF, DKIM and DMARC records tell receiving servers which mail is genuinely yours. Since 1 February 2024, Google's email sender guidelines have required all three for senders of more than 5,000 messages a day to Gmail accounts.
- Exposed services and software. Admin panels, test environments and outdated server software on any subdomain count against you. Our article on PHP2Shell vendor exposure shows how one outdated runtime can become an urgent supplier issue.
- Post-quantum readiness (Beta). Some checks now report whether your public endpoints use quantum-vulnerable key exchange, which matters for data that must stay confidential for years.
Privacy signals
- A published privacy policy that names the controller, explains purposes, and describes data subject rights.
- A cookie banner that offers a real choice before non-essential cookies load.
- Signals about cross-border data transfers and where data is hosted.
Exposure signals
Our glossary entry on darknet exposure explains these sources.
- Your domain appearing in known breach datasets.
- Corporate credentials in leaked password collections, infostealer logs or paste sites.
How to check your company's security posture: eight steps
List your domains, run an outside-in rating as a baseline, fix email, encryption, exposed services, privacy and credential findings, then re-check and keep evidence.
Steps 2–5 and 7 below rely on data a tool can collect automatically; deciding what to fix, changing configurations and updating policies is your team's work. How CyberRank helps: the rating automates the observation in steps 2–5 and 7, while your team owns the fixes.
- List your public domains. Include regional domains, campaign microsites and forgotten subdomains. Unknown assets are part of your attack surface whether you track them or not.
- Run an outside-in rating. Enter your main website URL in a rating tool and record the grade and findings as your baseline. CyberRank's step-by-step guide to the free security rating tool walks through the flow.
- Check email authentication. Confirm that SPF, DKIM and DMARC records exist for every sending domain. Move DMARC from p=none towards quarantine or reject once reports show legitimate mail passes.
- Review encryption and certificates. Disable TLS 1.0 and 1.1, support TLS 1.3, and track certificate expiry dates so they renew before they lapse.
- Close exposed services. Retire unused subdomains, take admin interfaces off the public internet, and patch software with known vulnerabilities.
- Read your privacy notice as a regulator would. The criteria in our quick answer on checking a vendor's privacy policy against UU PDP and GDPR apply equally to your own policy.
- Act on credential exposure. Reset affected passwords, enforce multi-factor authentication (MFA), and check the devices involved for infostealer malware.
- Re-check and keep evidence. Run the rating again after fixes, and keep a dated record of what changed for your next customer review.
How should you prioritise what you find?
Not every finding deserves the same urgency. The table below is a reasonable starting order; adjust it to your own systems and risk appetite.
Work from the top of the table below, fix in batches, and re-check after each batch so you can see the effect. How CyberRank helps: CyberRank prioritises vulnerability findings by severity and provides fix guides, so you can turn the table into a work plan.
| Finding | Suggested priority | First action | Usual owner |
|---|---|---|---|
| Active leaked credentials | Suggested priorityHigh | First actionReset passwords, enforce MFA, check devices | Usual ownerIT and security |
| Exposed admin interface | Suggested priorityHigh | First actionRestrict access or remove from the internet | Usual ownerInfrastructure |
| Outdated software with a known vulnerability | Suggested priorityHigh | First actionPatch or isolate; confirm the fix is serving traffic | Usual ownerInfrastructure |
| Expired or invalid certificate | Suggested priorityHigh | First actionRenew and automate renewal | Usual ownerInfrastructure |
| Missing DMARC record | Suggested priorityMedium | First actionPublish DMARC at p=none, then tighten | Usual ownerIT or email admin |
| TLS 1.0 or 1.1 still enabled | Suggested priorityMedium | First actionDisable legacy protocols | Usual ownerInfrastructure |
| Privacy policy missing rights or contact details | Suggested priorityMedium | First actionUpdate the policy | Usual ownerLegal and privacy |
| Cookie banner without a real choice | Suggested priorityMedium | First actionFix consent before non-essential cookies load | Usual ownerMarketing and legal |
Where CyberRank does not help
CyberRank sees only what is publicly observable. It cannot inspect your internal network, endpoints, access controls, backups or staff training, and it cannot tell whether your incident response plan works. A rating is a posture indicator, not a certification or an audit, and it does not make you compliant with NIS2, DORA, UU PDP or ISO/IEC 27001. It also cannot fix findings for you. For internal assurance, you still need internal audits, penetration testing, policy reviews and, where relevant, certification by an accredited body.
Conclusion
Checking your company's security posture from the outside is the quickest way to see what customers, attackers and auditors already see. Focus on five areas: encryption, email authentication, exposed services, privacy notices, and breach or credential exposure. Run a baseline, fix findings in priority order, re-check, and keep a dated record of the changes. That record turns a customer's vendor review from a surprise into a routine exchange of evidence. CyberRank's free rating gives you that baseline from a single URL, without registration to start.
References
- Verizon, 2025 Data Breach Investigations Report (April 2025)
- European Union, Directive (EU) 2022/2555 (NIS2), Article 21(2)(d) (14 December 2022)
- European Union, Regulation (EU) 2022/2554 (DORA), Article 28 (14 December 2022)
- ISO, ISO/IEC 27001:2022, Annex A controls 5.19–5.22 (October 2022)
- NIST, SP 800-52 Rev. 2: Guidelines for TLS Implementations (August 2019)
- Google, Email sender guidelines (requirements from 1 February 2024; accessed 16 November 2026)
Quick answers
Short, direct answers to questions this article raises.
- Quick answerHow to Improve Your Company's Security RatingThe fixes that most often move a security rating: TLS, DMARC, old subdomains and leaked credentials. How CyberRank re-rates after you fix them.
- Quick answerHow to Check if Company Credentials LeakedCheck whether your company's staff logins appear in breach data, infostealer logs or paste sites, and what to do next. With CyberRank's free check.
Related questions
Short answers that connect this article with our other guides.
Frequently asked questions
Check your company's security posture
Run the free Cybersecurity & Privacy Rating on your own website and see the grade your customers would see.
Check your company's security posture