🛡️ CIS LEBANON SECURITY INDEX™
Sunday, August 30, 2026
Methodology v3.0 · Coding Manual v3.1
OVERALL INDEX: 64 / 100
TREND: ⬇️ −9 (73 revised → 64), driven by Nabatieh. Yesterday's thin report was again substantially incomplete: fuller reporting establishes a multi-platform operation on 29 August across five locations, revising Nabatieh from 68 to 73. No new incidents were confidently dated overnight; confidence is LOW and CIS treats today's zero with the same caution.
TIER 1 — PUBLIC EDITION
🟠 NATIONAL ALERT LEVEL: 64/100 — HIGH
Driven by: Nabatieh · Trend: ⬇️ (revised basis — see note) · Confidence: LOW Spread: 0 CRITICAL · 1 HIGH · 1 MEDIUM · 5 LOW · 2 MINIMAL
Governorate Readings
| Governorate | Score | Level | Confidence |
|---|---|---|---|
| Nabatieh | 64 | 🟠 HIGH | LOW |
| South Lebanon | 33 | 🟢 LOW | LOW |
| Baalbek-Hermel | 24 | 🟢 LOW | LOW |
| Beqaa Valley | 22 | 🟢 LOW | LOW |
| Mount Lebanon | 22 | 🟢 LOW | LOW |
| Beirut | 20 | ⚪ MINIMAL | LOW |
| Akkar | 20 | ⚪ MINIMAL | LOW |
| North Lebanon | 18 | ⚪ MINIMAL | LOW |
| Keserwan-Jbeil | 16 | ⚪ MINIMAL | LOW |
> ⚠️ Yesterday's "thin" report was, again, substantially incomplete. Fuller reporting establishes a multi-platform operation on 29 August — aircraft, artillery and a drone-fired missile across five locations, not the single strike CIS coded at the time. Nabatieh's 29 August score revises from 68 to 73. This is the sixth time in two weeks that same-morning reporting has understated a night's activity, confirmed only once fuller detail emerged. CIS has swept for new activity overnight into today and found none confidently dated — treat that finding with the same caution.
No new incidents confidently dated to last night; yesterday revised sharply upward
- Fuller reporting on 29 August establishes a multi-platform operation across Nabatieh district: aircraft struck the al-Deir quarter and Ali al-Taher Hill area, artillery hit Haris and Haddatha, and a drone fired a guided missile onto a street in Nabatieh city itself — the first reported strike inside the city centre since this escalation began.
- CIS's overnight sweep for 29–30 August found no confidently dated new incidents at the time of compilation.
- The status of the Kfar Shuba position and the Haddatha–Aita al-Jabal vehicle movement, both reported on 27 August, remains unknown.
🚦 Zone Guidance
| Area | Guidance |
|---|---|
| Nabatieh city — including Nabih Berri Avenue | Avoid — drone-fired missile struck a city street 29 August |
| Al-Deir quarter (Nabatieh al-Fawqa) · Ali al-Taher hill · Haris · Haddatha | Avoid entirely — struck 29 August |
| Markaba · Rab el-Thalathine junction | Avoid |
| Kfar Shuba | Avoid entirely — status of the 27 August Israeli position unknown; treat as unresolved |
| Arab Salim · Braasheet · Srifa · Mansouri · Qantara · Kfar Rumman · Wadi al-Hujeir · Khiam | Avoid — struck this week |
| Israeli-controlled security zone (approx. 10 km deep) | Do not approach under any circumstances |
| Nabatieh district — Ansar, Deir al-Zahrani, Kfar Rouman, Harouf, Habboush | Avoid |
| Bint Jbeil, Marjayoun and Hasbaya districts | Avoid |
| Tyre district — routes south of Sidon | Avoid non-essential travel |
| Sidon and the coastal route | Passable — expect continued congestion |
| Dahiyeh · Bekaa Valley | Elevated caution |
| Beirut · Mount Lebanon · North Lebanon · Akkar · Keserwan-Jbeil | Normal operations; maintain situational awareness |
If you are in or near an affected area
- Do not travel into Nabatieh, Bint Jbeil, Marjayoun or Hasbaya districts.
- Note that a strike has now reached inside Nabatieh city itself, not only the outlying villages struck previously — adjust route planning accordingly if you transit the city.
- Do not treat a quiet-sounding report as confirmation of calm — this week's pattern has repeatedly shown otherwise, most recently yesterday.
- Keep phones charged and agree a family check-in time and a meeting point.
- Identify the lowest interior room in your building, away from windows and glazing.
- Keep identity documents, medication and cash together and ready to move at short notice.
- Follow Civil Defence (125) and Lebanese Red Cross (1760) in preference to social media.
📞 Emergency Contacts
- CIS Security emergency line (active clients): +961-3-539900 — 24/7/365
- CIS general enquiries: +961-3-539900 · info@cissecurity.net · Monday–Friday, 8:00 AM–6:00 PM
- Civil Defence: 125 · Lebanese Red Cross: 1760 · Internal Security Forces: 112
- Lebanese Army — South Lebanon Liaison: +961-8-802-510
- National Mental Health Lifeline: 1564 — free, confidential, 24/7
- US Embassy emergency (overseas citizens services): +1-202-501-4444 · BeirutACS@state.gov
> ⚠️ Responsible-use disclaimer > The CIS Lebanon Security Index™ is a professional situational assessment published as a free public service. It is informational — it is not a guarantee of safety and not a substitute for official government guidance. CIS Security accepts no liability for decisions made solely on Index readings. In an emergency, contact official emergency services. > Methodology: cissecurity.net/lebanon-security-index/#methodology · Corrections: cissecurity.net/lebanon-security-index/#corrections
Need security cover for a property or site? → https://app.cissecurity.net/request Get the Index in your inbox daily, 8:15 AM → cissecurity.net/lebanon-security-index/
CIS Security — Because Your Safety Isn't Optional — Since 1990
TIER 2 — ANALYST EDITION
⚠️ Revision Notice — REV-2026-009
29 August 2026 · Nabatieh · Published 68 · Revised 73.
Yesterday's edition coded a single incident for 29 August — a drone strike reported to have targeted Nabatieh al-Fawqa, per the Times of Israel, with no IDF comment. A Lebanese military field source, reported via a separate outlet, establishes a materially fuller picture: aircraft struck the al-Deir quarter of Nabatieh al-Fawqa and the Ali al-Taher Hill area; artillery hit the villages of Haris and Haddatha; a drone fired a guided missile onto Nabih Berri Avenue in Nabatieh city; and further strikes reportedly hit the junction area of Markaba and Rab el-Thalathine. CIS treats the al-Deir/Nabatieh al-Fawqa strike as the same incident already coded yesterday rather than double-counting it, and adds the four newly established locations.
Nabatieh's 29 August score revises from 68 to 73. Both figures remain permanently in the archive. Logged at cissecurity.net/lebanon-security-index/#corrections.
This is the sixth same-pattern revision since the methodology launched — 19, 20, 21, 22, 27, and now 29 August have all required upward correction after publication, in every case because same-morning sourcing had not caught up with the full scope of the preceding night. CIS addresses the implications of this pattern directly in §1 below, rather than restating it as a passing note for a sixth time.
1 · A Structural Finding, Not a Recurring Footnote
CIS first documented this pattern on 23 August, after four revisions in five days. It has now recurred twice more. CIS believes the pattern has moved from an observation to an established characteristic of covering this specific theatre, and states its practical implication plainly: any single day's published score in this Index should be read as a probable underestimate of that day's actual activity, pending revision. This does not mean the published figure is wrong at the time of publication — it is correctly computed from the best information available at 08:00 Beirut time — but readers, and CIS's own operational planning, should treat every fresh reading as a floor with a meaningful chance of moving upward over the following one to three days, not as a settled figure.
CIS is not changing its publication schedule or its methodology in response to this finding. Delaying publication to chase completeness would trade a worse problem (a stale or absent daily product) for a better-understood one (a same-day product that sometimes moves). CIS records this finding here so it is visible to any reader relying on the Index for planning, and will consider whether it warrants a standing note on the public methodology page at the 14 November calibration review.
2 · A Strike Reaches Nabatieh City Itself
Among yesterday's newly established incidents, the drone-fired missile onto Nabih Berri Avenue in Nabatieh city is notable for its location. Prior activity throughout this escalation, including the events of 27–28 August, has been concentrated in villages and rural areas around Ali al-Taher, Bint Jbeil district, and the Marjayoun and Hasbaya districts. Nabatieh city itself — the district capital and a significantly larger population centre — had not previously been struck in CIS's coded record of this escalation.
CIS assessment. CIS treats this as a meaningful, if isolated, expansion of the geographic scope of activity, distinct from the ground-vehicle movements CIS flagged as significant on 27–28 August. A strike reaching the district capital, even a single guided missile with no reported casualties, changes the risk calculus for clients and residents who had reasonably treated the city itself as outside the pattern of village-level strikes. CIS will monitor whether this is an isolated event or the beginning of activity extending into more populated areas.
3 · Today's Sweep
CIS's source sweep for the night of 29–30 August found no incident meeting the coding threshold at the time of compilation. This is recorded as a completed sweep with a genuine zero, consistent with the treatment of 17 August.
CIS assessment. Given the finding in §1, CIS assigns this zero even less confidence than usual. It is coded honestly because the completeness rule requires it, not because CIS believes it is likely to be the final word on the night of 29–30 August.
4 · Two Threads From 27 August Remain Unresolved
CIS has still not located further reporting on the Kfar Shuba position (flag raised, automatic fire opened) or the military vehicle movement reported near Haddatha toward Aita al-Jabal, both from 27 August. Their current status remains unknown for a second consecutive day.
5 · Coded Incident Log
30 August 2026 — decay 1.00
No incidents confirmed at time of compilation. Contribution: 0.0
29 August 2026 — decay 0.75 — REVISED (REV-2026-009)
| # | Governorate | Location | Category | Confirmation | Points |
|---|---|---|---|---|---|
| 1 | Nabatieh | Al-Deir quarter, Nabatieh al-Fawqa | Airstrike | Reported | 3.6 |
| 2 | Nabatieh | Ali al-Taher Hill area | Airstrike | Reported | 3.6 |
| 3 | Nabatieh | Haris, Bint Jbeil district | Artillery | Reported | 2.4 |
| 4 | Nabatieh | Haddatha, Bint Jbeil district | Artillery | Reported | 2.4 |
| 5 | Nabatieh | Nabih Berri Avenue, Nabatieh city | Explosive device (drone-fired guided missile) | Reported | 2.4 |
| 6 | Nabatieh | Markaba / Rab el-Thalathine junction | Airstrike | Reported | 3.6 |
Nabatieh subtotal: 18.00 (previously 3.60). All six incidents rest on a single field-source report and are coded Reported.
28 August 2026 — decay 0.5625
Eight incidents as coded in the 28 August edition. Nabatieh subtotal 16.80; South Lebanon subtotal 4.20.
27 August 2026 — decay 0.421875
Sixteen incidents as revised in the 28 August edition (REV-2026-008). Nabatieh subtotal 61.80; South Lebanon subtotal 3.60.
26 August 2026 — decay 0.316406
Seven incidents as coded in the 26 August edition. Nabatieh subtotal 24.00; South Lebanon subtotal 2.40.
25 August 2026 — decay 0.237305
Four incidents as coded in the 25 August edition. Nabatieh subtotal 13.20.
24 August 2026 — decay 0.177979
One incident as coded in the 24 August edition. Nabatieh subtotal 3.60.
23 August 2026 — decay 0.133484
Two incidents as coded in the 23 August edition. Nabatieh subtotal 7.20. This is the oldest day still inside today's window; it exits after tomorrow's edition.
22 August 2026
Fully exited the window as of today. No longer contributes at any weight.
6 · Scoring — Full Working
Nabatieh
| Component | Value |
|---|---|
| 30 August, decay 1.000000 | 0.00 |
| 29 August, decay 0.750000 (18.00 × 0.75, revised) | 13.50 |
| 28 August, decay 0.562500 (16.80 × 0.5625) | 9.45 |
| 27 August, decay 0.421875 (61.80 × 0.421875, revised) | 26.07 |
| 26 August, decay 0.316406 (24.00 × 0.316406) | 7.59 |
| 25 August, decay 0.237305 (13.20 × 0.237305) | 3.13 |
| 24 August, decay 0.177979 (3.60 × 0.177979) | 0.64 |
| 23 August, decay 0.133484 (7.20 × 0.133484) | 0.96 |
| Raw Load L | 61.35 |
| Activity = 75 × (1 − e^(−61.35/100)) | 34.39 |
| Structural baseline | 22 |
| National context modifier (active armed conflict) | 8 |
| Score | 64.39 → 64 🟠 |
South Lebanon
| Component | Value |
|---|---|
| 30 August, decay 1.000000 | 0.00 |
| 29 August, decay 0.750000 | 0.00 |
| 28 August, decay 0.562500 (4.20 × 0.5625) | 2.36 |
| 27 August, decay 0.421875 (3.60 × 0.421875) | 1.52 |
| 26 August, decay 0.316406 (2.40 × 0.316406) | 0.76 |
| Raw Load L | 4.64 |
| Activity = 75 × (1 − e^(−4.64/100)) | 3.40 |
| Structural baseline | 22 |
| National context modifier | 8 |
| Score | 33.40 → 33 🟢 |
Remaining seven governorates
No scoring incidents logged within the window. Activity 0.00. Score = baseline + modifier.
| Governorate | Baseline | Modifier | Score |
|---|---|---|---|
| Baalbek-Hermel | 16 | 8 | 24 🟢 |
| Beqaa Valley | 14 | 8 | 22 🟢 |
| Mount Lebanon | 14 | 8 | 22 🟢 |
| Beirut | 12 | 8 | 20 ⚪ |
| Akkar | 12 | 8 | 20 ⚪ |
| North Lebanon | 10 | 8 | 18 ⚪ |
| Keserwan-Jbeil | 8 | 8 | 16 ⚪ |
Parameters in force (frozen to 14 November 2026): methodology v3.0 · coding manual v3.1 · decay 0.75/day over 7 days · compression K=100 · activity ceiling 75 · fatality 8, injury 2, structure 3 capped at 12, displacement 5/district, route disruption 3 · confirmation multipliers 1.0 / 0.6 / 0.0.
7 · Confidence
Confidence remains LOW. Reported-share of Nabatieh's raw load is approximately 92%. Only the two Confirmed Ali al-Taher incidents from 27 August continue to provide corroborated weight in an otherwise entirely single-sourced window.
8 · What CIS Is Watching
- Whether today's zero-incident sweep is itself revised upward, consistent with the pattern documented in §1.
- Whether the strike on Nabatieh city proves isolated or is followed by further activity inside the city itself.
- Whether the Kfar Shuba position and the Haddatha–Aita al-Jabal vehicle movement are ever further reported on.
- Whether the 27–28 August escalation and its aftermath settle into a new, higher baseline or continue to decay toward the levels recorded before 27 August.
- Whether the Qatari mediation effort shows any results.
9 · CIS Operational Posture
CIS maintains Level 5 — Severe Alert.
A strike reaching Nabatieh city itself, combined with the now six-times-confirmed pattern of understated same-day reporting and two still-unresolved ground-movement threads from 27 August, together argue for sustained vigilance regardless of the Index's day-to-day movement.
(CIS Posture Levels 1–5: cissecurity.net/lebanon-security-index/#posture)
Practical effect for active client sites:
- Continuous supervisor contact for all sites in Nabatieh and South Lebanon governorates, now including Nabatieh city itself given yesterday's strike there.
- Reinforcement standby maintained under the 24/7 emergency line for active clients.
- Route and access planning reviewed daily for all southern sites, with particular attention to routes through Nabatieh city.
- New deployments continue within 24 hours of contract confirmation.
10 · Assessment
Today's headline number, 64, is less important than what produced it: a sixth confirmed instance of same-morning reporting materially understating a night's activity, this time by a wide margin — from one coded incident to six, including the first reported strike inside Nabatieh city itself.
CIS has moved from treating this as a recurring anomaly to stating it plainly as a structural feature of covering this theatre: every fresh Index reading should be read as a probable floor, not a settled figure, pending revision over the following one to three days. This does not compromise the Index's reproducibility — every score remains fully computed and auditable from its coded incident log — but it does mean readers should weight the trend across several days more heavily than any single morning's headline, a point CIS has made before and now states as a standing characteristic rather than a fresh caveat each time it recurs.
Substantively, the reach of yesterday's activity into Nabatieh city itself is the most significant single fact in this edition, ahead of the score's specific value. Combined with the still-unresolved Kfar Shuba and Haddatha threads from 27 August, CIS assesses that the past week has shown both a wider geographic footprint and less certainty about where currently active positions stand, even as the seven-day decay window continues to produce a number that moves within a familiar HIGH-band range.
For Beirut, Mount Lebanon, North Lebanon, Akkar and Keserwan-Jbeil, conditions remain calm and normal operations continue. The severity remains concentrated in Nabatieh, now including its district capital, and CIS states plainly that the geographic pattern of this escalation continues to widen even where the headline number does not always show it clearly on a given morning.
11 · Sources
Tier 2 — regional and national outlets Eastern Herald, citing a Lebanese military field source (29 August: al-Deir quarter, Ali al-Taher Hill area, Haris, Haddatha, Nabih Berri Avenue drone-fired missile, Markaba/Rab el-Thalathine junction).
Note under coding rule 4.6: all six incidents in the 29 August revision rest on a single field-source report and are coded Reported.
> ⚠️ Responsible-use disclaimer > The CIS Lebanon Security Index™ is a professional situational assessment published as a free public service. It is informational — it is not a guarantee of safety and not a substitute for official government guidance. CIS Security accepts no liability for decisions made solely on Index readings. In an emergency, contact official emergency services. > Methodology: cissecurity.net/lebanon-security-index/#methodology > Source register: cissecurity.net/lebanon-security-index/#sources > Corrections and revisions: cissecurity.net/lebanon-security-index/#corrections > To challenge a score: info@cissecurity.net with the date, governorate and basis.
Request security coverage → https://app.cissecurity.net/request Speak to CIS → +961-3-539900 · info@cissecurity.net
About CIS Security
CIS Security is one of Lebanon's most established security companies, providing professional security guard services across the country since 1990. From its headquarters in Jdeide, Beirut, CIS deploys 50+ licensed, uniformed guards on active duty nationwide, with more than 2,000 guards trained since 1990 and hundreds of properties protected.
CIS security services in Lebanon include residential security guards for towers, compounds and gated communities; commercial, retail and industrial security services; hospital and school security; jewelry store and high-value retail protection; executive protection and VIP services; and event security. These are supported by CCTV systems, electronic security and access control, GPS tracking and fleet management, risk assessment, professional security consulting, and crisis management and emergency response.
All CIS guard operations — recruitment, training, deployment and supervision — run under an ISO 9001:2015 certified quality management system, and every deployed guard holds a valid Lebanese security guard licence. Past contracts have included banks and financial institutions, embassies and diplomatic facilities, hospitals, and international organisations including UN agencies (UNICEF; UNGM vendor registration); references are available upon request. CIS teams work in Arabic, English and French.
New client deployments begin within 24 hours of contract confirmation, and a 24/7/365 emergency line is maintained for active clients. CIS Security also publishes the CIS Lebanon Security Index™, Lebanon's first daily public security intelligence platform, covering all nine governorates every morning at 8:00 AM.
Request a security quote → https://app.cissecurity.net/request Security guard jobs in Lebanon → https://hr.cissecurity.net Offices: Jdeide, Beirut · Monday–Friday, 8:00 AM–6:00 PM · +961-3-539900 · info@cissecurity.net
CIS Lebanon Security Index™ · Sunday, 30 August 2026 · Conflict Day 182 · Truce Day 71 Methodology v3.0 · Coding Manual v3.1 · Compiled in Beirut CIS Security — Because Your Safety Isn't Optional — Since 1990
