Country dossier

Mongolia

Worldwide badge coverage for Mongolia, grouped into seeded badges, event editions, add-ons, operational issues, resources, and evidence sources.

2 badge(s) · 2 event(s) · 1 series · 2025-2026

Back to countries

Seeded artifacts

Badges

2025

MNSEC 2025 Electronic Badge Collection

Completed 418-unit, three-variant MNCERT/CC electronic-badge collection

A completed MNSEC 2025 electronic-badge collection commissioned by MNCERT/CC and documented by Beelog Technologies. Beelog's public project page states that it designed, manufactured, and developed 418 electronic badges for MNCERT/CC; the public MNSEC2025BADGE archive identifies the order with the September cybersecurity conference, says three badge types were completed, and preserves Gerber, schematic, firmware, example-code, and supporting-material directories. The sources do not establish attendee allocation, a per-unit delivery record, final unit-by-unit configuration, safety validation, or reusable image provenance.

2026

MNSEC 2026 Event Badge

ESP32-C3 Wi-Fi stamp-passport badge for MNSEC13

An MNSEC 2026 (MNSEC13) event badge documented through a user-guide deck and front and back board renders uploaded on September 28, 2026 by the Beelog maintainer of the MNSEC 2025 badge archive. The guide, headed MN CERT/CC 2026, describes a badge that joins the MNSEC Badge Cloud over event Wi-Fi, shows booth stamps, a contact card, and badge status, and reacts with light, sound, and vibration; its Stamp Passport collects stamps from 14 sponsor booths for a prize draw.

Events

Camp and Event Editions

MNSEC 2025

MNSEC · Shangri-La Ulaanbaatar Hotel ballroom, Ulaanbaatar, Mongolia · 2025 · 1 badge(s)

The completed September 25, 2025 MNSEC Cybersecurity Conference in Ulaanbaatar, themed Cyber Resilience. MNCERT/CC's official event posts establish the conference context, while Beelog Technologies and its public MNSEC2025BADGE archive identify a completed custom MNCERT/CC electronic-badge order: 418 badges across three types. The public project tree preserves source material, but does not establish attendee allocation, final unit-by-unit configuration, delivery recipients, safety validation, or reusable image rights.

MNSEC 2026

MNSEC · Shangri-La Ulaanbaatar, 19 Olympic Street, Sukhbaatar District, Ulaanbaatar, Mongolia · 2026 · 1 badge(s)

The September 24, 2026 thirteenth MNSEC cybersecurity conference, organized by MNCERT/CC at the Shangri-La Ulaanbaatar under the Security Beyond Human Scale theme with the Haruul Zangi national CTF final. The official site, checked September 29 and 30, 2026 after the elapsed date, still reads pre-event with sold-out tickets and publishes no badge statement, so the edition is not marked completed; a September 28 upload by the Beelog maintainer of the MNSEC 2025 badge archive adds an MNSEC13 event-badge user guide and board renders, while attendee allocation and handoff stay unverified.

Lifecycle

Add-ons & Upgrades

MNSEC 2026 Event Badge documented in user guide

badge game mechanic

14-booth Stamp Passport

Staff at 14 sponsor booths stamp the badge using the attendee's registered phone number; the badge responds with LEDs, buzzer, and vibration, and collecting all 14 stamps enters the prize draw.

MNSEC 2025 Electronic Badge Collection manufacturer-reported completed custom order

completed delivery context

418-unit MNCERT/CC custom-order delivery record

Beelog's official project page says it designed, manufactured, and developed 418 electronic badges for MNCERT CC as a custom order. The companion archive identifies MNSEC 2025 and says the work was completed, but neither source publishes ticket eligibility, recipient identities, handoff records, or evidence that all conference attendees received a badge.

MNSEC 2025 Electronic Badge Collection source archive published

hardware documentation

Public schematic and Gerber material

The repository preserves two schematic PDFs and three Gerber archives alongside support material. These public documents make the collection technically discoverable, but are not presented as build, repair, power, safety, fabrication, or all-unit-parity instructions.

MNSEC 2025 Electronic Badge Collection source archive published

software source context

Public firmware and example-code material

The project tree contains a firmware binary, a named sketch, and component-oriented examples. This establishes a public software trail without reproducing connectivity, configuration, update, or operating instructions or claiming a final deployed image for every delivered unit.

MNSEC 2025 Electronic Badge Collection public Gerber and repository description

variant design archive

Three named badge-design variants

The source archive says three badge types were completed and publishes named Gerber archives for Albat, HaruulZangi, and Humun. This preserves the documented multi-variant design trail without assigning a particular unit, role, or feature set to an attendee or assuming each archive exactly matches final delivered production.

Operational history

Issues & Camp Impact

attendee allocation, recipient, and handoff boundary · manufacturer project page and public source archive · completed quantity reported; recipient outcome unrecovered

Beelog reports that 418 electronic badges were delivered to MNCERT CC as a custom order, and the archive says the MNSEC 2025 badge work was completed. The reviewed public sources do not publish ticket eligibility, role allocation, recipient identities, registration linkage, pickup location, handoff report, returns, replacements, or evidence that every conference attendee received a badge.

The catalogue records a completed event-associated badge collection without making an attendee-wide allocation or individual delivery claim.

design-file and licence gap · repository contents · documentation-only archive

Unlike the BSD 2-Clause MNSEC2025BADGE archive, the 2026 repository contains only a user-guide PDF and two renders, with no licence, schematic, Gerber, BOM, or firmware; the module and display identification comes from the render silkscreen rather than a parts list.

Hardware claims stay at the level visible in the guide and renders, and the 2025 licence is not carried over to the 2026 material.

firmware release and operational-configuration boundary · public firmware directory and README · binary, sketch, and examples available; final deployment record unrecovered

The repository provides a firmware binary, a named sketch, and examples, but it does not document a signed or reconciled final release, source-to-unit mapping, dependency lockfile, update/support policy, final connectivity configuration, service availability, data practice, or privacy policy. No credentials or operational configuration details are reproduced in this record.

Public source material remains linkable without claiming a reproducible, supported, secure, current, or uniform operational setup for delivered badges.

issuance and completion gap · official site plus builder documentation · organizer wrap-up and handoff unverified

The official MNSEC site still read pre-event on September 29, 2026, five days after the September 24 date, and the badge repository publishes a pre-event user guide and renders without a production count, attendee allocation, or distribution statement.

The edition is not marked completed and the record does not assert that every attendee received the badge.

missing rights-cleared image · local project policy · needs licensed original replacement

No MNSEC 2025 Electronic Badge Collection image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The Mongolia record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

multi-variant hardware and final-unit mapping gap · public repository tree · three design archives visible; production mapping unrecovered

The repository describes three badge types and publishes three named Gerber archives plus two schematic PDFs. It does not publish a reconciled production BOM, revision history, component-substitution record, test plan, final assembly record, per-variant quantity split, or mapping from technical files to each delivered badge.

The entry keeps the collection-level hardware description bounded and does not imply that every unit had identical hardware, display, sensors, power, firmware, or physical finish.

power, sensor, and electrical-safety gap · public archive review · design materials visible; safety validation unrecovered

The archive includes schematic, Gerber, sensor, and example-code material, but reviewed public sources do not establish final battery chemistry, charging/protection behavior, power budget, electrical limits, thermal result, sensor calibration, component substitutions, assembly quality control, certification, compliance, or a universal safe-use outcome.

The record documents a real completed electronic badge collection without treating open project material as independently validated operating, fabrication, repair, or safety guidance.

source-license, media-rights, and branding scope boundary · repository license and public-site review · BSD source/binary license recorded; selected-image rights unresolved

The repository root publishes a BSD 2-Clause license credited to DavgaBeelog, while Beelog's current public site reserves its own rights. The reviewed archive and event pages do not pair a selected factual physical badge photo or upstream render with a complete source URL, image-specific reuse basis, attribution, and processing provenance. The BSD source/binary statement is not assumed to licence all photographs, renders, artwork, brands, or physical artifacts.

The catalogue links the source archive and license but publishes no local badge image until an image-specific rights-cleared source is available.

Resources

Sources