Security engineering
Reviews, hardening, bot and abuse defence, and privacy compliance.
One to four weeks for a review.
A review across the application, dependencies, hosting and data handling, then remediation, then a re-test. Bot and abuse controls tuned so scrapers and scanners are stopped without blocking search engines and social previews along with them.
Launch is close and nobody has looked at the security, the bot exposure or the data-handling obligations.
A review across the application, dependencies, hosting and data handling, then remediation, then a re-test. Bot and abuse controls tuned so scrapers and scanners are stopped without blocking search engines and social previews along with them.
A written report you can hand to a customer, the findings fixed, and an edge configuration that survives the first week of internet attention.
Reviews, hardening, bot and abuse defence, and privacy compliance.
One to four weeks for a review.
Donations, fundraising, participant and volunteer management, and the reporting a board and a funder both need.
Security review, automated usability testing, vulnerability scanning in CI, and the edge and bot policy that keeps a product reachable but not scrapeable.
Vulnerability scanning that runs offline, cyber ranges, bot and abuse defence, and vision systems for sites where footage cannot leave the premises.
Last reviewed · Site changelog