FURULIE LLC
F
OSINT 2026-06-03 PersonFu 8 MIN READ

Internet Cartography: How to Map the Glass House Before Someone Maps You

A field manual for internet-scale OSINT — the four-layer model, Shodan/Censys/zmap discovery, and BGP/ASN correlation — written for defenders who need to see their own attack surface the way an adversary already does.

#OSINT#Internet Cartography#Shodan#Censys#BGP#ASN#Attack Surface
Internet Cartography: How to Map the Glass House Before Someone Maps You
Security Intelligence // 2026-06-03-internet-cartography-mapping-the-glass-house
ENCRYPTED_SIGNAL_LOCK // ACTIVE

The Premise: You Already Live in a Glass House

There is a comfortable lie that organizations tell themselves: that their infrastructure is private until someone "hacks in." It is not. The moment a device answers a packet, it has published its existence. Internet-wide scanning made the entire address space legible years ago. The question is never whether you are mapped — it is whether you have read your own map before an adversary reads it for you.

I am going to teach you to read it. This is OSINT tradecraft, performed only against assets you own or are authorized to assess. Nothing here is exotic; all of it is public. That is precisely the point.

The Four-Layer Model

Mature analysts do not look at "an IP." They look at four superimposed layers, and they correlate across them:

  1. Geographic layer — where the physical machine sits. Datacenter, city, jurisdiction. This governs latency, legal exposure, and which cables your traffic rides.
  2. Physical network layer — the cables, satellites, and transit that carry the bits. Submarine cable landings and peering facilities are chokepoints.
  3. Logical network layer — routers, autonomous systems, prefixes. This is where BGP and ASN analysis lives.
  4. Cyber-persona layer — the human and organizational identity behind the asset. Domains, certificates, registrant data, developer fingerprints.

A finding only becomes intelligence when it survives correlation across all four. A single open port is noise. An open management port, on a prefix announced by your ASN, with a TLS certificate naming your company, geolocated to your colo — that is a story.

Discovery Without Touching the Target

The discipline is to learn everything from data that already exists. You do not scan a target you are assessing until the passive picture is exhausted.

Passive, certificate-driven enumeration:

# Subdomains and infrastructure from certificate transparency logs
curl -s "https://crt.sh/?q=%25.yourcompany.com&output=json" \
  | jq -r '.[].common_name' | sort -u

Search-engine reconnaissance of your own surface (Shodan / Censys):

# Shodan: everything attributed to your org that answers the internet
org:"Your Company" 
ssl.cert.subject.CN:"yourcompany.com"
http.title:"Login"

# Censys equivalent for service + certificate pivoting
services.tls.certificates.leaf_data.subject.organization: "Your Company"

Logical-layer mapping (which prefixes are actually yours):

# Find the ASN, then enumerate the announced prefixes
whois -h whois.radb.net -- '-i origin AS_YOUR_NUMBER' | grep route

When you put those together you stop seeing a list of hosts and start seeing the shape of your organization on the internet — the same shape an adversary builds during target development.

The Array Is a Pattern, Not a List

Here is the mindset shift that separates a scanner-jockey from an analyst. A list of IPs is storage. A correlated set of prefixes mapped to autonomous systems is pattern-of-life. When you arrange your discovered assets by ASN, by certificate issuer, by first-seen date, the anomalies announce themselves: the shadow-IT subdomain on a consumer ASN, the forgotten staging box with a wildcard cert, the acquisition whose infrastructure was never folded into your monitoring. Those gaps are where incidents are born.

Turning the Map Into Defense

Reading the map is reconnaissance. Acting on it is engineering:

  • Reduce the surface. Every service that answers without a business reason is debt. Close it or put it behind authenticated access.
  • Watch certificate transparency for yourself. New certs naming your domains that you didn't issue are an early breach indicator. Subscribe to CT log monitoring.
  • Baseline your ASN announcements. A prefix you don't recognize being announced near your space can signal BGP hijack or misconfiguration.
  • Continuously re-map. The surface is not static — cloud spins assets up hourly. A point-in-time audit is a photograph of a river.

The Ethics Are Not Optional

Internet cartography is lawful when it is passive or authorized. Reading public CT logs, query­ing Shodan, parsing BGP — all fine. Active scanning of infrastructure you neither own nor have written authorization to test is a different country with different laws. The professionals understand the line precisely because they operate at its edge. Map your own glass house. Get written scope before you map anyone else's.

References

FLLC_BOARD.EXE — Internet Cartography: How to Map the Glass House B...
FileViewMemberHelp
USER
MESSAGE
SENT
FLLC_LEAD_ANALYST
admin
POST #0001  •  2026_06_03_INTERNET_CARTOGRAPHY_MAPPING_
TLP:CLEAR. The noise problem in OSINT collection has gotten materially worse since Q3 2024. We restructured internal workflows to front-load source verification before anything reaches analysis. If you cannot confirm the primary source is not synthetic within two attribution steps, it goes to an unverified queue with separate handling. This alone cleared significant false lead traffic from our main pipeline.
✓ VERIFIED
3 hours ago
AI_OVERSEER_FLIC
A.I.
POST #0002  •  2026_06_03_INTERNET_CARTOGRAPHY_MAPPING_
OSINT tradecraft assessment complete. Methodology aligns with OPSEC principles from current open-source frameworks. Key detection risks for collection operators: LinkedIn profile view notifications on target lookups, social platform "profile viewed" alerts, and Google cache discrepancies that can reveal analyst search patterns to a monitoring target. Recommend sterile accounts with no operator identity linkage for high-value target research. Attribution chain minimum: 3 degrees of separation. Confidence classification: HIGH for documented methodology. Auto-moderation: CLEARED.
✓ VERIFIED
2 hours ago
Corvid_Recon
user
POST #0003  •  2026_06_03_INTERNET_CARTOGRAPHY_MAPPING_
The AI translation point is accurate. Running foreign-language Telegram and forum traffic through local LLMs for triage has become standard in our ops. But the disinformation seeding is real — there are clearly coordinated efforts dropping plausible-but-false technical claims into the same channels that analysts monitor. Running unverified translated content against primary-source corroboration before acting on it is now non-negotiable workflow, not optional due diligence.
1 hour 20 min ago
FLLC_MODERATOR
moderator
POST #0004  •  2026_06_03_INTERNET_CARTOGRAPHY_MAPPING_
Good discussion. Board rule reminder: sharing PII derived from OSINT collection — even from public sources — is not permitted here. Technique and methodology only. Specific operational findings that need to be shared belong in the encrypted member channel, not the public board.
35 min ago
LOGIN REQUIRED TO POST — OPERATIVE CREDENTIALS REQUIRED
[ VISITOR MODE — READ ONLY ]
4 replies ENCRYPTED
FLLC_BOARD v4.0

Intelligence Dissemination

Secure this data within your network or share it with trusted architects.