Hotspots create the edge network
Each hotspot is a real gateway serving real users. TaraSec does not need to wait for a separate security-only infrastructure before testing and expanding the cooperative model.
DEMO 4 — ISP CHALLENGE
Let hotspots behind NAT participate in cooperative cybersecurity.
Demo 4 addresses a practical deployment problem: a TaraSec hotspot may sit behind ordinary carrier or ISP NAT, so another network cannot reliably identify that hotspot by its public source address. TaraSec therefore needs a trusted path for tagged traffic that works at scale without requiring every hotspot to have its own public IP address.
WHY DEMO 4 EXISTS
Commercial hotspot deployment and ISP cooperation should reinforce each other.
TaraSec hotspots can be deployed for an immediate economic reason: they provide connectivity and can generate local income. Demo 4 shows how that growing hotspot footprint can also become useful security infrastructure.
NAT should not exclude participation
Many hotspots use ordinary consumer or mobile Internet connections and sit behind NAT. Their public source address may be shared, dynamic or controlled by the access provider.
Telecom participation increases the value
If telecoms and ISPs participate in TaraSec, they can recognize a TaraSec partner routing path and act on the security information carried with traffic from many downstream hotspots.
TARGET FLOW
Route tagged traffic through an identifiable TaraSec endpoint.
The target design is simple in principle:
1. Customer trafficLeaves a TaraSec hotspot
2. TaraSec classificationTraffic is already tagged as suspicious when appropriate
3. Tagged pathOnly the relevant tagged traffic uses the designated TaraSec route
4. Stable partner identityThe receiving ISP sees the known TaraSec endpoint
5. ISP actionThe receiving network can combine endpoint trust with the TaraSec tag
Normal customer traffic should continue to use its normal route. Demo 4 is about making tagged traffic attributable to a cooperating TaraSec path, not about tunnelling all hotspot traffic through a central service.
NOT WHITELISTING
The TaraSec endpoint identifies the partner path; it does not make the traffic safe.
A receiving ISP should not trust traffic merely because it came through a TaraSec router. The routing endpoint answers a different question: which cooperating network is asserting this security information?
Endpoint identity
The public TaraSec router or equivalent endpoint gives the receiving ISP a stable partner identity even when thousands of originating hotspots are behind different NAT systems.
Security classification remains separate
The TaraSec tag describes the traffic or sender state. A suspicious tag remains suspicious. The known endpoint should make the classification more useful, not override it.
Designed for automation
The long-term goal is for cooperating networks to handle the tagged path automatically under agreed policy rather than maintaining manual per-hotspot exceptions.
WHY TELECOMS MATTER
A telecom can help turn hotspot growth into network-scale security cooperation.
A telecom may provide connectivity to many TaraSec hotspots while also participating in TaraSec's security exchange. This creates a useful feedback loop: hotspot revenue supports deployment, deployment produces more participating edge networks, and telecom participation makes the cooperative security layer more useful.
Demo 4 is therefore not only a technical routing experiment. It demonstrates how the income-producing hotspot network can grow into ISP-scale TaraSec infrastructure.