Founded by West Point graduates
Strategic security leader with operational experience across Central Asia, the Middle East, Europe, the United States, and the Caucasus. Specializes in building organizational security capacity from the ground up, helping institutions establish practical, resilient, and scalable security structures in complex environments. Former Army infantry officer in the NATO Response Force. Holds a BA from West Point and an MA from King’s College London.
Security and risk management leader with over 25 years of experience across the Middle East, Africa, and emerging markets. Specializes in crisis management and establishing organizational security capabilities in complex environments. Former U.S. Army Counterintelligence Special Agent and Foreign Service Officer, with senior leadership roles at Coca-Cola and SOS Children’s Villages International. Holds graduate degrees from Columbia University and Georgia State University.
Security risk and crisis management professional with over 13 years of experience in domestic and international operations. Specializes in protective intelligence, geopolitical risk analysis, emergency management, and strategic planning, helping organizations anticipate threats and strengthen operational resilience in complex environments. Experienced in coordinating security operations with government agencies, international partners, and key stakeholders. Graduate of the United States Military Academy at West Point.
Strategy and operations leader with a background spanning military leadership and management consulting. He commanded combat units as a commissioned officer before transitioning into management consulting, where he advised Fortune 500 companies on large-scale transformations, operational improvement, and business continuity. He holds a B.S. from the United States Military Academy at West Point and an LL.B. from Georgian-American University.
Technology and project management professional with experience overseeing large-scale initiatives in defence, security technology, and artificial intelligence. Specializes in coordinating complex technology projects and developing practical solutions that support organizational decision-making and operational effectiveness. Previously worked as an analyst at the National Bank of Georgia, bringing an analytical perspective to technology and innovation. Studied public and economic policy at the London School of Economics.
Security technology specialist with experience building data-driven solutions that support security risk and intelligence operations. Specializes in developing Big Data and ETL pipelines, as well as software tools for travel security, emergency alerts, and threat-informed decision support. Additional expertise includes digital forensics and information security. Holds a BA in Computer Science from West Point.
We bring together the people and expertise your assignment needs.
Your people. Your locations. Your priorities.
Explore a public example of our operational risk assessment.
Reference risk profile · Kyiv City
Latest individual evidence review: 29 October 2026
Highest assessed risk per category · 1–25
47 risks assessed · 10 categories · Review dates vary by risk
Choose a region to see how local conditions could affect your people, travel and plans.
The operator report does not establish route-wide interruption, restoration, or freight availability.
Staff movements and project handoffs that depend on Dnipro passenger rail may be delayed or interrupted if the relevant service is affected. Cargo availability and freight capacity are not established by this passenger-train report.
Before dispatch or a staff movement, check the current operator notice for the actual service and confirm the onward handoff and a workable alternative.
Evidence reviewed 29 October 2026 · Analysis updated 29 October 2026
A Dnipro station strike makes the relevant rail service worth checking before staff travel or a project handoff; it does not establish a route-wide closure.
The operator report does not establish route-wide interruption, restoration, or freight availability.
Planning connections to check for your operation
Use current operator information for the station and train required; this report does not establish present availability.
Confirm the receiving contact, timing tolerance and an appropriate alternative.
Update the affected team and provider instead of assuming the original connection remains usable.
Conditional review points to agree for your operation
The operator reports a suspension, restriction, or change affecting the planned service.
Reassess the movement and onward connection before dispatch.
The operator confirms service restoration or a changed arrangement.
Verify that the actual departure, arrival and handoff meet the operation’s timing needs.
Scope Operator reported a strike at Dnipro station on 29 October; current service status is unverified
A team can have a usable workplace and still lose the connection staff need to reach it. Check the actual journey and shift handover before relying on a cross-river metro connection. The notice does not establish a road-bridge closure.
Confirm the current line status and a workable alternative before setting staff arrival or handover times.
Evidence reviewed 29 October 2026 · Analysis updated 28 October 2026
Check who can reach the site before confirming the shift. A working office does not establish a working cross-river journey.
Planning connections to check for your operation
Use the operator’s current status for the actual stations and travel time; this assessment does not confirm restoration.
Assign a contact and an authorized fallback journey or adjusted start when the required connection is unavailable.
Tell the receiving team and staff together so the original pickup or handover plan is not used after it stops working.
Conditional review points to agree for your operation
The operator confirms restoration of the affected section.
Recheck the actual journey before returning to the previous shift or pickup arrangement.
The fallback loses required access, shelter or arrival time.
Change the activity or attendance arrangement under the organization’s plan; do not assume another route is automatically suitable.
Scope Operator notice · 27 October; present service must be checked
Jet-powered variants · daytime exposure
Red + yellow warnings. Not working hours lost.
Overnight-only assumptions leave staff journeys, office hours and critical tasks exposed. Faster drones can compress the time available to act.
Plan shelter access and movement decisions for the working day as well as overnight.
Evidence reviewed 29 October 2026 · Analysis updated 19 October 2026
Daytime attacks bring shelter and movement decisions into the working day. Staff need a plan for home, the journey and the office.
Jet-powered variants · daytime exposure
Red + yellow warnings. Not working hours lost.
Planning connections to check for your operation
Identify accessible shelter at the site and along essential movements. Check access arrangements before relying on them.
Make clear who pauses work, accounts for staff and confirms the next step after an interruption.
Identify tasks that can move, pause or be handed over without leaving people dependent on one location.
Conditional review points to agree for your operation
Warning time or shelter access no longer supports the planned movement.
Reassess the journey or attendance arrangement before it is repeated.
A sustained change in timing, speed or targeting alters the exposure of your sites.
Review the working-day plan and the tasks that require physical presence.
Scope Persistent change in the threat
Decision pathway; no improvement in availability or recovery time is implied.
Operators and public authorities now have a broader stated coordination remit, but site continuity still depends on actual local service and restoration notices. Do not reduce backup or change project assumptions based on the organizational decision alone.
Keep current continuity arrangements in place and look for implementation evidence before changing operating assumptions.
Evidence reviewed 29 October 2026 · Analysis updated 29 October 2026
Ukraine expanded cross-sector emergency coordination, but the decision does not prove improved restoration or local service availability.
Decision pathway; no improvement in availability or recovery time is implied.
Planning connections to check for your operation
Do not reduce backup or continuity measures solely because the coordination remit expanded.
Use dated notices relevant to the site and service before changing attendance or delivery plans.
Assess whether verified response changes affect the particular operation or dependency.
Conditional review points to agree for your operation
Authorities or operators publish evidence of a material implementation or response change.
Reassess only the continuity assumptions affected by that evidence.
A local operator reports an outage, restriction or restoration affecting a required service.
Review the site, staff or project fallback against the actual notice.
Scope Resolution adopted; implementation and service outcomes not established
Newest event dates first. Continuing developments retain their original dates. Measurements show their own weekly periods.
The operator report does not establish route-wide interruption, restoration, or freight availability.
Staff movements and project handoffs that depend on Dnipro passenger rail may be delayed or interrupted if the relevant service is affected. Cargo availability and freight capacity are not established by this passenger-train report.
Before dispatch or a staff movement, check the current operator notice for the actual service and confirm the onward handoff and a workable alternative.
Evidence reviewed 29 October 2026 · Analysis updated 29 October 2026
A Dnipro station strike makes the relevant rail service worth checking before staff travel or a project handoff; it does not establish a route-wide closure.
The operator report does not establish route-wide interruption, restoration, or freight availability.
Planning connections to check for your operation
Use current operator information for the station and train required; this report does not establish present availability.
Confirm the receiving contact, timing tolerance and an appropriate alternative.
Update the affected team and provider instead of assuming the original connection remains usable.
Conditional review points to agree for your operation
The operator reports a suspension, restriction, or change affecting the planned service.
Reassess the movement and onward connection before dispatch.
The operator confirms service restoration or a changed arrangement.
Verify that the actual departure, arrival and handoff meet the operation’s timing needs.
Scope Operator reported a strike at Dnipro station on 29 October; current service status is unverified
A team can have a usable workplace and still lose the connection staff need to reach it. Check the actual journey and shift handover before relying on a cross-river metro connection. The notice does not establish a road-bridge closure.
Confirm the current line status and a workable alternative before setting staff arrival or handover times.
Evidence reviewed 29 October 2026 · Analysis updated 28 October 2026
Check who can reach the site before confirming the shift. A working office does not establish a working cross-river journey.
Planning connections to check for your operation
Use the operator’s current status for the actual stations and travel time; this assessment does not confirm restoration.
Assign a contact and an authorized fallback journey or adjusted start when the required connection is unavailable.
Tell the receiving team and staff together so the original pickup or handover plan is not used after it stops working.
Conditional review points to agree for your operation
The operator confirms restoration of the affected section.
Recheck the actual journey before returning to the previous shift or pickup arrangement.
The fallback loses required access, shelter or arrival time.
Change the activity or attendance arrangement under the organization’s plan; do not assume another route is automatically suitable.
Scope Operator notice · 27 October; present service must be checked
Jet-powered variants · daytime exposure
Red + yellow warnings. Not working hours lost.
Overnight-only assumptions leave staff journeys, office hours and critical tasks exposed. Faster drones can compress the time available to act.
Plan shelter access and movement decisions for the working day as well as overnight.
Evidence reviewed 29 October 2026 · Analysis updated 19 October 2026
Daytime attacks bring shelter and movement decisions into the working day. Staff need a plan for home, the journey and the office.
Jet-powered variants · daytime exposure
Red + yellow warnings. Not working hours lost.
Planning connections to check for your operation
Identify accessible shelter at the site and along essential movements. Check access arrangements before relying on them.
Make clear who pauses work, accounts for staff and confirms the next step after an interruption.
Identify tasks that can move, pause or be handed over without leaving people dependent on one location.
Conditional review points to agree for your operation
Warning time or shelter access no longer supports the planned movement.
Reassess the journey or attendance arrangement before it is repeated.
A sustained change in timing, speed or targeting alters the exposure of your sites.
Review the working-day plan and the tasks that require physical presence.
Scope Persistent change in the threat
Decision pathway; no improvement in availability or recovery time is implied.
Operators and public authorities now have a broader stated coordination remit, but site continuity still depends on actual local service and restoration notices. Do not reduce backup or change project assumptions based on the organizational decision alone.
Keep current continuity arrangements in place and look for implementation evidence before changing operating assumptions.
Evidence reviewed 29 October 2026 · Analysis updated 29 October 2026
Ukraine expanded cross-sector emergency coordination, but the decision does not prove improved restoration or local service availability.
Decision pathway; no improvement in availability or recovery time is implied.
Planning connections to check for your operation
Do not reduce backup or continuity measures solely because the coordination remit expanded.
Use dated notices relevant to the site and service before changing attendance or delivery plans.
Assess whether verified response changes affect the particular operation or dependency.
Conditional review points to agree for your operation
Authorities or operators publish evidence of a material implementation or response change.
Reassess only the continuity assumptions affected by that evidence.
A local operator reports an outage, restriction or restoration affecting a required service.
Review the site, staff or project fallback against the actual notice.
Scope Resolution adopted; implementation and service outcomes not established
Newest event dates first. Continuing developments retain their original dates. Measurements show their own weekly periods.
Businesses need to separate continuity of a signed commitment from decisions requiring a new minister, agency approval or public-sector counterpart. Local staff movement still needs a protest contingency.
Identify approvals and counterpart decisions that could fall during the handover.
Evidence reviewed 29 October 2026 · Analysis updated 28 October 2026
Plan around the government handover and local disruption; recognition of an election result alone does not establish new operating rules.
Planning connections to check for your operation
List the decisions that depend on public authorities and the person currently authorized to make them.
Check the applicable process with the responsible agency and contract owner.
Review local gatherings, transport and communications before staff travel.
Conditional review points to agree for your operation
A new administration or agency head is appointed.
Reconfirm the responsible counterpart and any delegated signing authority.
A demonstration affects the planned route.
Use the agreed alternative route or meeting arrangement.
Scope Government formation and policy implementation remain separate milestones
Connection schematic. Launch does not measure uptime.
A new backbone route can widen provider choices, but local last-mile and shared upstream dependencies still need testing.
Ask whether your backup connection uses a genuinely separate route.
Evidence reviewed 29 October 2026 · Analysis updated 19 October 2026
A new cable can widen backup options. Its value depends on whether your service uses a separate, tested route to the site.
Connection schematic. Launch does not measure uptime.
Planning connections to check for your operation
Check the proposed service route and any shared infrastructure with the existing connection.
Verify that the required systems and communications work through the alternative.
Revisit the dependency map when providers or routing arrangements change.
Conditional review points to agree for your operation
The proposed services share a dependency that can interrupt both.
Review another continuity option before counting the second service as independent.
The fallback fails the test required for a critical task.
Revise the service or the operating fallback before relying on it.
Scope Connection launched
Procurement, employment and market-entry plans need to follow implementation, rather than assume all EU rules already apply.
Track the rules affecting your contracts, customs and staff.
Evidence reviewed 18 October 2026 · Analysis updated 19 October 2026
Accession progress signals future change. Business obligations depend on implemented rules and effective dates, so commitments need activity-specific checks.
Planning connections to check for your operation
Identify the customs, product, contract and employment questions relevant to the assignment.
Review the actual implementation and confirm applicability with qualified advisers.
Confirm that the arrangements still match the rules applying to the transaction.
Conditional review points to agree for your operation
A national implementation measure changes a requirement relevant to your activity.
Review the affected contract or process with the appropriate adviser.
A confirmed effective date conflicts with the planned transaction.
Reassess timing and required preparation before committing.
Scope Negotiations opened
Counterparty→Ownership chain
Names and controlBank / intermediary→End use
Applicable restrictionsPreviously screened suppliers and intermediaries may need a fresh check before payment or shipment.
Refresh relevant counterparty and ownership checks before committing funds.
Evidence reviewed 27 October 2026 · Analysis updated 19 October 2026
A previous screening result can become outdated. Recheck counterparties, ownership and payment or shipment intermediaries before execution.
Counterparty→Ownership chain
Names and controlBank / intermediary→End use
Applicable restrictionsPlanning connections to check for your operation
Review the named counterparty, ownership and intermediaries against current applicable restrictions.
Obtain qualified sanctions advice and resolve identification issues before proceeding.
Agree when changes in listings, ownership or payment arrangements require another check.
Conditional review points to agree for your operation
A listing or ownership change may connect to the transaction.
Re-screen the relevant parties and seek specialist advice on applicability.
The payment or shipment chain introduces an unresolved intermediary.
Resolve that exposure before the commitment is executed.
Scope Restrictions adopted
Staff activity→Movement plan
Civic and protest exposureAccess decision→Support limits
Distinct permission and support constraintsPublic-facing work, local partners and movements near protest sites require a different review from routine office journeys.
Review staff activity and routes separately from occupied-area access.
Evidence reviewed 29 October 2026 · Analysis updated 19 October 2026
Staff exposure depends on their role, activity and route. Public-facing work, protests and occupied-area access need separate arrangements.
Staff activity→Movement plan
Civic and protest exposureAccess decision→Support limits
Distinct permission and support constraintsPlanning connections to check for your operation
Identify public-facing tasks and the legal and access questions they create.
Review protest-adjacent journeys separately from occupied-area access.
Make clear who reviews enforcement changes and who staff contact if arrangements fail.
Conditional review points to agree for your operation
Enforcement changes affect the activity assigned to staff or partners.
Review that task and obtain relevant local advice.
A protest or access restriction affects the planned route.
Reassess the journey and its alternative before movement.
Scope Continuing constraint
Newest event dates first. Continuing developments retain their original dates. Measurements show their own weekly periods.
Companies with Saudi and Red Sea dependencies should review escalation exposure while keeping current service availability separate from authorization and potential retaliation.
Set the deployment, targeting and transport changes that would trigger a review of the operation.
Evidence reviewed 29 October 2026 · Analysis updated 28 October 2026
The authorization is confirmed. Decisions about staff and cargo should follow actual participation, targeting and access changes.
Planning connections to check for your operation
Identify Saudi operations and Red Sea-linked movements that depend on the same route or provider.
Assign responsibility for reviewing confirmed participation and access changes.
Reassess the actual site, journey or shipment instead of treating the entire region as equally affected.
Conditional review points to agree for your operation
A deployment or credible targeting change affects the client footprint.
Reassess the relevant staff and site arrangements.
A provider changes acceptance or a relevant access restriction takes effect.
Review the booked movement and activate an appropriate fallback.
Scope Authorization confirmed; deployed-force details not established
Route schematic, not incident coordinates. Events: 16 Oct.
Reported incidents near Oman and Iraq reinforce review of the full voyage, including approaches and onward legs. Do not infer responsibility or current traffic levels from these reports; verify carrier acceptance, port access, cover and delay contingencies for the specific shipment.
Build contingencies for the whole voyage, including Gulf approaches.
Evidence reviewed 18 October 2026 · Analysis updated 19 October 2026
The voyage depends on more than the strait crossing. Review approaches, port calls, carrier acceptance and onward delivery together.
Route schematic, not incident coordinates. Events: 16 Oct.
Planning connections to check for your operation
Map approaches, waiting areas, port calls and the onward leg against the intended operation.
Verify carrier acceptance, port conditions and insurance arrangements with the responsible specialists.
Agree contingency timing, routing and who can authorize a change.
Conditional review points to agree for your operation
An incident or access change affects a leg of your planned voyage.
Reassess the full route and the consequences for delivery.
Carrier acceptance or cover terms cease to support the movement.
Review the commercial commitment and alternative with the relevant specialists.
Scope Route-specific review required
Aden airport→Onward travel
2 missiles reported · 16 OctBab el-Mandeb→Red Sea / Suez
Shipping threat remainsAir access, port calls and Red Sea routing are connected dependencies. A land advance does not establish safe commercial passage.
Keep alternate arrival and cargo routes in the same operating plan.
Evidence reviewed 29 October 2026 · Analysis updated 19 October 2026
An accessible airport or port does not guarantee a usable journey. Check the arrival point and onward connection together.
Aden airport→Onward travel
2 missiles reported · 16 OctBab el-Mandeb→Red Sea / Suez
Shipping threat remainsPlanning connections to check for your operation
Check the specific airport, airline, port or carrier arrangements required for the movement.
Review the alternative arrival point and onward route as one complete option.
Update receiving teams and providers before continuing with the amended journey.
Conditional review points to agree for your operation
A service suspension or access notice affects the planned arrival.
Reassess the arrival point and onward arrangements together.
The destination remains accessible but its connecting route is disrupted.
Review the full movement before treating destination access as sufficient.
Scope Airport and sea-route exposure
Newest event dates first. Continuing developments retain their original dates. Measurements show their own weekly periods.
Mobilization teams should distinguish the rollout date from the mandatory date. An authorization, a visa-free stay allowance and permission to work address different questions.
Check passport, entry point, travel date and the applicable exemption before mobilizing staff.
Evidence reviewed 29 October 2026 · Analysis updated 28 October 2026
November begins the rollout; the guidance keeps authorization recommended during the transition. Check each traveler’s actual status and dates.
Planning connections to check for your operation
Match the actual airport or land crossing and intended entry date to the rollout.
Check the official exemption and separate entry, stay and work rules.
Add the process and the stated application lead time to future mobilization planning.
Conditional review points to agree for your operation
An implementation date or exemption changes.
Recheck affected bookings against the official guidance.
A traveler changes passport or immigration status.
Check whether the existing authorization and other permissions still apply.
Scope Recommended during transition; specified cases become mandatory from July 2027
Power-dependent staff operations and projects in Kyrgyzstan should check their own continuity arrangements and monitor peak-period supply notices. The national demand signal is not a site-level availability assessment or evidence of scheduled restrictions.
Review critical loads and tested backup, and monitor official peak-period notices before relying on uninterrupted power.
Evidence reviewed 29 October 2026 · Analysis updated 29 October 2026
Kyrgyzstan’s reported autumn demand record warrants continuity checks for power-dependent work, but does not establish an outage at any site.
Planning connections to check for your operation
Confirm which work must continue and whether the facility’s backup has been tested for those loads.
Use current operator or authority information; do not treat the demand record alone as a restriction notice.
Reassess the affected task and backup against the actual notice and the facility’s requirements.
Conditional review points to agree for your operation
An official notice announces a supply restriction or materially changed peak-period conditions.
Reassess the affected activity against its power requirements and tested backup.
A facility’s power or backup fails its required operating test.
Pause or relocate the affected work under the organization’s continuity plan and verify recovery before resuming.
Scope Autumn demand record reported 27 October; no outage established
Decision schematic. No route availability or transit-time measurement is implied.
Cargo and project plans still depend on the sea crossing, onward rail, customs handoffs and the services a carrier can actually commit to.
Keep present lead-time and contingency assumptions until the booked route and each handoff are confirmed.
Evidence reviewed 29 October 2026 · Analysis updated 27 October 2026
The policy direction supports longer-term diversification. Commit today’s cargo against confirmed services and handoffs.
Decision schematic. No route availability or transit-time measurement is implied.
Planning connections to check for your operation
Obtain confirmation for the crossing, onward transport and customs handoff.
Use effective rules and operating services when revising lead times.
Rebook or reroute against the project’s delivery tolerance.
Conditional review points to agree for your operation
An applicable customs rule takes effect.
Check the shipment’s documentation and clearance plan against the implemented rule.
A carrier confirms capacity and the onward connection.
Reassess the schedule, recovery margin and alternative routing for that booking.
Scope Implementation and shipment performance require separate confirmation
Projects can expand future capacity while local connection, distribution and backup requirements remain immediate operating issues.
Check the site connection and backup needs against commissioning dates.
Evidence reviewed 29 October 2026 · Analysis updated 19 October 2026
Planned generation is not usable supply at your site. Base current continuity decisions on the actual connection and tested backup.
Planning connections to check for your operation
Review connection requirements, critical loads and the existing fallback.
Record which commissioning and connection milestones the operating plan assumes.
Check that the service needed by the site is available and performs as required.
Conditional review points to agree for your operation
A delivery milestone changes the basis of an expansion plan.
Reassess the operational start date and interim arrangements.
The current site supply or backup fails the required operating test.
Review continuity measures without waiting for future capacity.
Scope Agreements signed
Connection schematic, not a measured service-quality claim.
Route diversification can improve continuity options, but two providers may still share the same last mile or upstream infrastructure.
Test route independence before counting a second connection as backup.
Evidence reviewed 29 October 2026 · Analysis updated 19 October 2026
A second provider may share the same failure point. Verify route independence and test the systems your operation needs.
Connection schematic, not a measured service-quality claim.
Planning connections to check for your operation
Ask how the proposed service reaches the site and where it overlaps with the primary connection.
Verify the essential systems through the alternative under the agreed test conditions.
Define who changes the connection and how the primary service is checked before return.
Conditional review points to agree for your operation
A primary and backup service share a critical failure point.
Review a more independent route or another operating fallback.
Provider changes invalidate the tested service path.
Recheck independence and repeat the relevant continuity test.
Scope Connection launched
Role + location→Movement exposure
Gender-specific constraintsAccess plan→Practical fallback
Check who can perform the workA staffing or service-delivery plan that ignores gender-specific movement and enforcement exposure can fail even when a route is physically open.
Review who can deliver the work, where and under what access constraints.
Evidence reviewed 29 October 2026 · Analysis updated 19 October 2026
Access restrictions can change who can deliver the assignment. Check staffing, travel and service access together before committing.
Role + location→Movement exposure
Gender-specific constraintsAccess plan→Practical fallback
Check who can perform the workPlanning connections to check for your operation
Check the activities and movement required of each participant with appropriate local advice.
Confirm that the proposed team and delivery arrangements are workable.
Reassess tasks, access, support and escalation together with the people affected.
Conditional review points to agree for your operation
Enforcement affects the staff or participants needed for the assignment.
Reassess the delivery model and protection arrangements before continuing.
A proposed workaround transfers exposure to another group or role.
Review that consequence explicitly before adopting the alternative.
Scope Documented access exposure
Newest event dates first. Continuing developments retain their original dates. Measurements show their own weekly periods.
Local knowledge.Founded by West Point graduates. Shaped by the places we know and the people we support.
Mitigate Risk was founded in 2019 by West Point graduates from a very dynamic part of the world. We’ve lived and worked here for years, and our understanding of the region, its cultures, religions, societies and languages comes from being part of it.
With years of experience in security operations, we stepped up to serve organizations in our own backyard, and have since supported operations in the most critical environments. We bring professional experience and personal knowledge to help clients navigate the challenges here, starting with listening to what they actually need.
You are paying for practical security support, not large firm overhead. Our approach is lean, direct, and designed to deliver serious support without inflated consulting fees.
We do not hand over recycled templates. Every assessment, plan, and recommendation is shaped around your people, your exposure, and the decisions you actually need to make.
Our advice comes from people working in the environments clients care about, not distant teams removed from the reality on the ground.