BastionGuard is intentionally not an all-encompassing security solution. It is designed around explicit threat boundaries, deterministic behavior, and visible enforcement.
This page documents what BastionGuard does not attempt to protect against, by design. These are not missing features — they are deliberate non-goals.
1. Nation-State or Advanced Persistent Threats (APT)
BastionGuard does not claim to protect against highly resourced attackers, nation-state actors, or long-term targeted intrusion campaigns.
- No memory introspection or kernel-level behavioral tracing
- No heuristic user behavior profiling
- No covert anomaly detection
BastionGuard focuses on explicit, enforceable policies, not invisible adversarial detection.
2. Zero-Day Exploits in Trusted Software
BastionGuard does not attempt to detect unknown zero-day vulnerabilities inside trusted or already-installed software.
- No runtime exploit prediction
- No speculative vulnerability blocking
- No in-memory exploit detection
BastionGuard assumes that software integrity and patching are handled through standard system update mechanisms.
3. User Intent and Social Engineering Decisions
BastionGuard does not override user intent. If a user explicitly allows an action, BastionGuard respects that decision.
- No automatic override of confirmed user actions
- No behavioral nudging or manipulation
- No silent prevention of user-approved operations
Security decisions remain visible and reversible, but never silently enforced against the user.
4. Cloud Account Compromise Outside the Local System
BastionGuard does not monitor or protect third-party cloud accounts beyond explicit breach intelligence checks.
- No live monitoring of external services
- No credential harvesting detection
- No continuous identity surveillance
Identity breach monitoring is on-demand and informational, not persistent or invasive.
5. Network Intrusion Detection Systems (IDS/IPS)
BastionGuard is not a full network IDS or IPS.
- No deep packet inspection
- No traffic anomaly scoring
- No passive network surveillance
Network enforcement is limited to deterministic rules derived from phishing intelligence and explicit policies.
6. Obscured or Hidden Automation
BastionGuard intentionally avoids features that act without clear visibility or traceability.
- No background decision engines
- No hidden trust scoring
- No silent remediation
If BastionGuard takes action, the user can see it, understand it, and audit it.
Design Principle: Explicit Limits
A security system that claims to protect against everything cannot be reasoned about.
BastionGuard defines clear boundaries to ensure that its protections remain understandable, predictable, and trustworthy.
Anything outside these boundaries is intentionally left to other layers of the system or to informed user decisions.