No major high-value public reconnaissance artifact was exposed in the bounded checks.
foodbankindonesia.com/
The integrated level cannot be determined because the foundational WebSec result is unavailable.
This level describes observed exposure within the bounded assessment scope. It does not mean the site is currently compromised and it is not a substitute for a professional penetration test.
AI-Resilience Scorecard
Safe boundary checks produced meaningful external evidence without claiming penetration-test coverage.
Explicit automation friction was limited within the bounded request budget.
Harmless mutation variants remained within generally stable response boundaries.
Observable public prerequisites for attack chaining were assessed without executing an exploit chain.
Public defensive signals were assessed; internal detection and recovery operations remain outside external verification.
Findings & Evidence
Recon Resistance
Finding: No major high-value public reconnaissance artifact was exposed in the bounded checks.
Score basis: Public artifact exposure, metadata, error disclosure, technology leakage and route behavior.
Limitation: Authenticated and non-linked private routes are not enumerated.
Recommendation: Reduce unnecessary technology, metadata and artifact exposure; review public routes after material changes.
Exploit Resistance
Finding: Safe boundary checks produced meaningful external evidence without claiming penetration-test coverage.
Score basis: Safe input, parser, browser-policy and HTTP-method boundary observations; destructive exploit classes are intentionally not executed.
Limitation: No destructive SQL injection, XSS, SSRF, command injection, traversal or upload exploitation is performed.
Recommendation: Strengthen input validation, parser boundaries, CSP/CORS and server-side controls; use authorized deep testing for exploit classes.
Automation Resistance
Finding: Explicit automation friction was limited within the bounded request budget.
Score basis: Repeated bounded requests, explicit bot identity, rate-control signals, status consistency and response timing.
Limitation: No load/DoS test, credential stuffing or high-volume scraping is performed.
Recommendation: Add explicit rate controls, bot/abuse detection and graduated friction for machine-speed behavior.
Adaptive Resistance
Finding: Harmless mutation variants remained within generally stable response boundaries.
Score basis: Harmless case, encoding, path and query mutations used to observe canonicalization and response consistency.
Limitation: No exploit-bearing mutation or multi-turn autonomous exploitation is performed.
Recommendation: Normalize inputs consistently and validate encoded or canonicalized variants at the same security boundary.
Chaining Resistance
Finding: Observable public prerequisites for attack chaining were assessed without executing an exploit chain.
Score basis: Combined observation of exposed artifacts, verbose errors, secret-like material, CORS and metadata as possible attack-chain prerequisites.
Limitation: No credential use, persistence, lateral movement or authenticated exploit chain is performed.
Recommendation: Minimize public prerequisites that can be combined into an attack chain; review secrets, errors, CORS and exposed artifacts together.
Detection & Recovery
Finding: Public defensive signals were assessed; internal detection and recovery operations remain outside external verification.
Score basis: Externally observable edge controls, security contact publication, abuse friction and error hygiene.
Limitation: Internal logging, alerting, incident response and backup/restore readiness cannot be proven from public HTTP behavior.
Recommendation: Improve observable abuse controls and verify internal logging, alerting, incident response and restore readiness through authorized internal review.
Context-aware AI-resilience interpretation
Foundational web-security context is broadly consistent with the observed AI-resilience posture. The final level still remains constrained by the weakest material autonomous-attack domain and evidence coverage.
Priority interpretation: Strengthen Detection & Recovery & Exploit Resistance first, then reassess to verify whether the attack path has materially narrowed.
Focus remediation where observed resistance is lowest.
Improve observable abuse controls and verify internal logging, alerting, incident response and restore readiness through authorized internal review.
Strengthen input validation, parser boundaries, CSP/CORS and server-side controls; use authorized deep testing for exploit classes.
AI-Resilience Assessment Review
The bounded external assessment produced an AI.RESWA measurement score of 58.4/100. The integrated WebSec × AI.RESWA result is MODERATE EXPOSURE. Evidence coverage reached 80%.
The integrated level cannot be determined because the foundational WebSec result is unavailable.
Prioritize Detection & Recovery & Exploit Resistance. Reassess after material security changes to measure whether observed resistance improves.
AVALUE AI.RESWA reports the integrated LEVEL by correlating the independent AI.RESWA measurement with the independent AVALUE WebSec foundation result. AI-resilient does not mean AI-proof.
Bounded external assessment with Evidence Coverage 80%. Unknown or internally unverifiable controls are not treated as PASS. The assessment intentionally avoids brute force, denial-of-service, destructive exploitation, exfiltration and persistence.