Security posture reviews
Review the assets, accounts, configurations, and business workflows in scope. Document what was checked, the evidence behind each finding, and practical remediation priorities.
A prioritized action planSecurity work should account for your actual systems and the consequences of a change. I focus on clear findings, prioritized remediation, and a useful handoff.
Review the assets, accounts, configurations, and business workflows in scope. Document what was checked, the evidence behind each finding, and practical remediation priorities.
A prioritized action planReview multi-factor authentication, administrative roles, account recovery, shared access, and offboarding. Reduce unnecessary access and document who owns each system.
Clearer control of important accountsAssess agreed authentication flows, exposed files, dependencies, deployment configuration, and application behavior. Review AI-generated code, implement practical hardening, and verify fixes. Penetration testing uses defined targets, methods, and explicit authorization.
Verified application security improvementsPerform authorized server penetration testing and review VPS, container, firewall, patching, and remote-access configuration. Harden local AI hosts and configure Tailscale or comparable private network access with defined users and permissions.
Tested exposure and clearer access boundariesReview DNS ownership, email authentication, backups, restore procedures, and recovery access. Check that the team can find the documentation and knows what to do when something fails.
Better prepared for disruptionAssess authorized models and custom AI applications for jailbreaks, prompt injection, unintended disclosure, and tool-access failures. Define test boundaries, preserve reproducible evidence, recommend mitigations, and retest agreed fixes.
Scoped findings for AI-specific risksExplore a typical workflow. These are illustrative scenarios; the details and results depend on the agreed project.
Important accounts have shared logins, unclear owners, and inconsistent offboarding.
A reviewed access model establishes named owners, appropriate permissions, MFA, and a documented process for joining or leaving the team.
An application is live, but exposed files, dependencies, and configuration have not had a focused review.
The agreed scope is assessed, findings are prioritized by impact and evidence, and fixes are tested before a controlled release.
A server or container stack grew over time, leaving services, credentials, and maintenance responsibilities difficult to track.
A scoped inventory and hardening plan clarifies exposure, patching, permissions, backups, and how the team recovers access.
Staff use several AI tools without a clear policy for data, connected accounts, or approval of actions.
Approved tools and data boundaries are documented, access is scoped, and people practice when to review or escalate an AI-generated action.
Define the systems, authorization, access, constraints, and business priorities before assessment work begins.
Collect evidence, distinguish confirmed findings from hypotheses, and rank improvements by risk and effort.
Make agreed changes through staging or a controlled change process, then retest the affected behavior.
Record the changes, remaining issues, ownership, recovery steps, and any follow-up support scope.
Security findings need context. I explain what was observed, what remains uncertain, and what a change will affect before recommending the next step.
scope: approved systems and test methods
evidence: findings with reproducible context
priority: business impact + exposure
changes: agreed, reversible where possible
verification: retest affected behavior
handoff: owners, recovery, remaining risksStart with a focused review, a defined project, or ongoing support. The scope, costs, and responsibilities are agreed before work begins.
Get an evidence-based view of a website, deployment, account environment, or AI workflow.
Implement the agreed improvements with attention to business continuity and handoff.
Review changes and maintain a practical security baseline as your systems evolve.
I offer scoped security posture reviews, identity and access hardening, website and application reviews, cloud and server configuration work, recovery readiness, and AI risk reviews. Each engagement defines the systems, authorized methods, deliverables, and verification work in writing.
I offer authorized penetration testing for agreed server, application, and AI-system targets, including jailbreak assessments for models and custom AI applications. Scope, test methods, access, operating constraints, and reporting are agreed before work starts. Emergency incident response or a staffed SOC is a separate service requirement.
No provider can guarantee that. The objective is to understand exposure, reduce avoidable risk, and improve the ability to detect, respond, and recover. A review records the work performed and its limitations rather than presenting a permanent security guarantee.
Yes. I can assess agreed parts of an existing application, its dependencies, access flows, deployment, and connected tools. Findings are evaluated against the actual context, and remediation can be scoped and verified separately.
Changes can affect access and integrations, so we plan them around the system and your operating requirements. Appropriate work includes backups, staging or controlled rollout, rollback notes, verification, and a clear owner for recovery access.
A review can help identify technical and operational gaps relevant to your requirements and produce useful evidence of remediation. Legal interpretations, formal certifications, insurer approval, and regulated assessments require the relevant qualified parties; they are not implied by a general security review.
Hardening can address technical gaps against agreed industry or organizational requirements and produce evidence of the work performed. Compliance also depends on policies, operations, contracts, and the applicable assessment process. I coordinate technical readiness with your responsible advisers; I do not promise blanket compliance or issue regulatory certifications.
Tell me what you are working on, what is getting in the way, and what a useful result would look like.
Based in San Francisco. Available for Bay Area projects and remote collaboration.