モダンなサイバーセキュリティ監視・インシデント対応システムの設計 Wazuh・SOAR・脅威インテリジェンスを用いた実践的アーキテクチャ

なぜ多くのセキュリティプロジェクトは最初から失敗するのか

多くの日本企業が「セキュリティを強化したい」と考えていますが、実際には次のような状況に陥りがちです。

  • アラートは大量に出るが、誰も対応しない
  • 高価な製品を導入したが、現場で使いこなせない
  • 見た目の良いダッシュボードはあるが、実害を防げない
  • 特定の担当者に依存し、その人が不在になると運用が止まる

本当の問題はツールそのものではありません。
問題はシステム設計(System Design)です。

本記事では、私たちが実際の現場で採用している 実運用に耐えるサイバーセキュリティ監視・対応システム の設計思想とアーキテクチャを、日本企業の運用・監査・ガバナンスを前提として解説します。

Continue reading "モダンなサイバーセキュリティ監視・インシデント対応システムの設計 Wazuh・SOAR・脅威インテリジェンスを用いた実践的アーキテクチャ"

การออกแบบระบบ Cybersecurity Monitoring & Incident Response สมัยใหม่ สถาปัตยกรรมเชิงปฏิบัติ ด้วย Wazuh, SOAR และ Threat Intelligence

ทำไมหลายโครงการด้านความปลอดภัยไซเบอร์ในไทยถึงล้มเหลวตั้งแต่เริ่ม

หลายองค์กรในประเทศไทยอยากได้ “ระบบความปลอดภัยที่ดีขึ้น” แต่สิ่งที่ได้จริงมักเป็น:

  • แจ้งเตือนจำนวนมาก แต่ไม่มีใครตอบสนอง
  • เครื่องมือราคาแพงที่ทีมใช้งานไม่เป็น
  • Dashboard สวย แต่ไม่ช่วยป้องกันเหตุจริง
  • ระบบที่พึ่งพาคนเก่งไม่กี่คน ถ้าคนนั้นไม่อยู่ ทุกอย่างหยุด

ปัญหาที่แท้จริง ไม่ใช่เครื่องมือ
แต่คือ การออกแบบระบบ (System Design)

Continue reading "การออกแบบระบบ Cybersecurity Monitoring & Incident Response สมัยใหม่ สถาปัตยกรรมเชิงปฏิบัติ ด้วย Wazuh, SOAR และ Threat Intelligence"

Building a Modern Cybersecurity Monitoring & Response System. A Practical Architecture Using Wazuh, SOAR, and Threat Intelligence

Building a Modern Cybersecurity Monitoring & Response System

A Practical Architecture Using Wazuh, SOAR, and Threat Intelligence

Why most security projects fail before they start

Many organizations want “better security”, but what they usually get is:

  • Too many alerts, no action
  • Expensive tools nobody understands
  • Security dashboards that look good but don’t protect anything
  • A system that depends on a few individuals’ knowledge

The real problem is not tools.
It’s system design.

This article explains how we design a production-ready cybersecurity monitoring & response system—one that is practical, auditable, and automatable—and why this architecture works in the real world.


The real objective (not marketing buzzwords)

The goal is not “installing SIEM” or “using AI”.

The real objectives are:

  1. Detect real threats, not noise
  2. Know who must respond, and when
  3. React fast before damage spreads
  4. Keep evidence for audit & investigation
  5. Stay flexible and vendor-neutral

This is a system engineering problem, not a product selection problem.


The architecture philosophy

We deliberately separate responsibilities.

Detection ≠ Automation ≠ Escalation ≠ Investigation

Each part must do one job extremely well.


The core stack we use (and why)

System architecture overview

graph TD
    A["Endpoints / Servers / Cloud"] --> B["Wazuh Agent"]
    B --> C["Wazuh Manager (SIEM/XDR)"]
    C --> D["Shuffle SOAR"]
    D -->|Create / Update Incident| E["DFIRTrack"]
    D -->|SEV-1 / SEV-2| F["PagerDuty"]
    D -->|Automated Response| G["Firewall / DNS / IAM / EDR"]

    F --> H["On-call Engineer"]

This diagram shows how detection, automation, escalation, and investigation are cleanly separated but tightly integrated.

1. Detection layer — Wazuh

Wazuh acts as the security sensor network:

  • Collects logs from:

    • Firewall
    • DNS
    • IDS / IPS
    • VPN
    • Servers & endpoints
  • Normalizes events
  • Applies correlation rules

Wazuh answers:
“Something suspicious happened. What is it?”

We do not overload Wazuh with business logic.
Its job is detection, not decision-making.


2. Automation & decision layer — SOAR (Shuffle)

Once something is detected, we need logic:

  • Is this serious?
  • Is this known malicious?
  • Should we block, alert, or just log?

This is where SOAR comes in.

Shuffle allows us to build explicit security playbooks:

  • Threat-intelligence enrichment
  • Severity calculation
  • Conditional response
  • System-to-system orchestration

Shuffle answers:
“What should we do next?”

This is where engineering experience matters most.


3. Guaranteed human response — PagerDuty

Automation is powerful—but humans are still responsible.

PagerDuty ensures:

  • The right person is notified
  • Escalation happens if no one responds
  • Response time is measurable (SLA)

PagerDuty answers:
“Who is responsible right now?”

This is the difference between alerts and accountability.


4. Investigation & audit trail — DFIRTrack

Every serious event becomes an incident:

  • Evidence
  • Timeline
  • Decisions
  • Actions taken

DFIRTrack provides:

  • Incident records
  • Asset tracking
  • Investigation notes
  • Audit readiness

DFIRTrack answers:
“What happened, exactly?”

This is essential for compliance, post-incident review, and trust.


How real use cases are implemented

Example 1: DNS communication to malicious domains

Problem
Malware almost always uses DNS to “phone home”.

System behavior

  1. DNS logs are collected
  2. Domain is compared against live threat-intelligence feeds
  3. If malicious:

    • Incident is created
    • Endpoint is identified
    • Firewall/DNS block is applied
    • On-call engineer is notified (if severity is high)

This detects attacks before data is stolen.


Example 2: IDS / IPS traffic to known attacker IPs

Problem
Some attacks bypass endpoint security.

System behavior

  • IDS/IPS logs are analyzed
  • Destination IP matches known attacker infrastructure
  • Correlated with asset criticality
  • Automated containment or escalation

This avoids “signature spam” and focuses on real risk.


Example 3: VPN login success from outside Thailand

Problem
A successful login can still be an attack.

System behavior

  • VPN authentication logs analyzed
  • GeoIP enrichment applied
  • If login is successful from unexpected country:

    • Risk score increases
    • Incident created
    • Optional forced verification or temporary block

This detects credential theft, not just brute force.


Why threat intelligence must be always fresh

Attackers rotate:

  • Domains
  • IPs
  • Infrastructure

That’s why we build:

  • Scheduled IOC updates
  • Confidence scoring
  • Expiration handling
  • Automated enforcement updates

Security systems that rely on static rules become obsolete fast.


Why this architecture scales (and survives audits)

  • Modular
  • Vendor-neutral
  • Open-source friendly
  • Easy to extend
  • Clear responsibility boundaries

This system works for:

  • SMEs
  • Factories
  • Enterprises
  • Managed security services (MDR)

Why clients hire us to build this

Because we don’t:

  • Install tools and disappear
  • Sell dashboards without response
  • Hide logic inside black boxes

We design systems:

  • With clear intent
  • With documented logic
  • With measurable outcomes

Security is not about tools.
It’s about decisions, timing, and responsibility.


If you are planning a similar system

If you’re thinking:

  • “We want better security visibility”
  • “We need real incident response, not alerts”
  • “We want something we can understand and control”

Then this architecture is a strong foundation.

If you want it designed and implemented correctly,
with real operational experience behind it—

Let’s talk.


Final thought

Good security systems don’t feel complicated.
They feel calm, predictable, and under control.

That’s the system we build.

AI 时代的经典编程思想

为什么“传统思想”在今天反而更重要

AI 可以比任何工程师更快地写代码。它可以在几秒钟内生成模块、重构代码、给出解决方案。但越来越多的团队正在发现一个看似矛盾的事实:

AI 用得越多,经典编程思想就越重要。

本文将解释:为什么诞生于几十年前的编程原则,在 AI 时代不仅没有过时,反而成为 AI 能否被正确使用的前提条件

Continue reading "AI 时代的经典编程思想"

AI時代におけるクラシック・プログラミングの考え方

なぜ「古い考え方」が今こそ重要なのか

AIは人間よりも速くコードを書きます。モジュール全体を生成し、リファクタリングを行い、問題解決案を数秒で提示することも可能です。しかし、多くの組織が次のような一見矛盾した事実に気づき始めています。

AIを使えば使うほど、クラシックなプログラミングの考え方が重要になる

本記事では、数十年前から存在するプログラミングの原則が、なぜ今も不可欠であり、むしろAI活用を「成立させる前提条件」であるのかを解説します。

Continue reading "AI時代におけるクラシック・プログラミングの考え方"

แนวคิดการเขียนโปรแกรมแบบคลาสสิกในยุค AI

ทำไมแนวคิดเก่ายังคงสำคัญกว่าที่เคย

AI สามารถเขียนโค้ดได้เร็วกว่าใครในทีม มันสร้างโมดูลทั้งชุด รีแฟกเตอร์ไฟล์ และเสนอแนวทางแก้ปัญหาได้ภายในไม่กี่วินาที แต่หลายองค์กรเริ่มพบความจริงที่ดูย้อนแย้งว่า

ยิ่งเราใช้ AI มากเท่าไร แนวคิดการเขียนโปรแกรมแบบคลาสสิกยิ่งสำคัญมากขึ้นเท่านั้น

บทความนี้อธิบายว่าทำไมหลักคิดที่เกิดขึ้นมานานหลายสิบปีจึงยังจำเป็น และเหตุใดแนวคิดเหล่านี้จึงเป็นสิ่งที่ ทำให้ การพัฒนาซอฟต์แวร์ด้วย AI มีประสิทธิภาพ ไม่ใช่ถูกแทนที่

Continue reading "แนวคิดการเขียนโปรแกรมแบบคลาสสิกในยุค AI"

SimpliPOSFlex. 面向真实作业现场的 POS 系统(中国市场版)

面向真实作业现场的 POS 系统(中国市场版)

在这类业务中,每一秒都是成本,每一次失误都会侵蚀利润,而任何不清晰的数据都会演变为经营风险。

想象一下清晨的回收场景:卡车陆续进场,工作人员将废料放到电子地磅上,重量稳定后,数据自动进入 POS 系统,凭条即时打印,结算金额当场确认。无需手写记录,也无需再录入 Excel,更不会在事后因为“重量不一致”而产生纠纷。

Continue reading "SimpliPOSFlex. 面向真实作业现场的 POS 系统(中国市场版)"

SimpliPOSFlex 現場の「現実」に向き合うためのPOS(日本市場向け)

現場の「現実」に向き合うためのPOS(日本市場向け)

このような業務では、1秒の遅れがコストになり、1つのミスが利益を削り、曖昧さは必ずリスクになります。

朝のリサイクルヤードを想像してください。トラックが次々と到着し、作業員がスクラップを計量器に載せる。重量が安定すると同時に数値がPOSに自動入力され、伝票が即座に印刷され、支払額がその場で確定します。手書きは不要、Excelへの転記も不要、後から「重量が違う」というトラブルも起きません。

Continue reading "SimpliPOSFlex 現場の「現実」に向き合うためのPOS(日本市場向け)"

SimpliPOSFlex. The POS Designed for Businesses Where Reality Matters

The POS Designed for Businesses Where Reality Matters

Imagine a recycle yard on a busy morning: a truck unloads scrap metal, the operator places it on the scale, weight stabilizes, a receipt prints instantly, and payment is calculated on the spot. There is no spreadsheet, no manual typing, and no argument later about what really happened.

Most POS systems are built for shops that sell items.
But many real businesses don’t sell “items” — they sell weight, grade, material, evidence, and trust.

Recycle factories, agricultural buying stations, refill shops, pawn shops, industrial receiving yards — these businesses live in the physical world, not spreadsheets.

SimpliPOSFlex was created for them.


Why Generic POS Systems Fail in Specialized Businesses

In many factories and yards, we see the same problems:

  • Weight is read manually and typed into the system
  • Prices are overridden without trace
  • Disputes happen because there is no evidence
  • Internet downtime stops operations
  • Data privacy is unclear or risky

Generic POS software treats hardware as an afterthought, when in reality hardware is the workflow itself.
In reality, hardware **is the workflow**.


What Is SimpliPOSFlex?

SimpliPOSFlex is a specialized Android POS platform designed for businesses where:

  • Transactions depend on measurement (weight, volume, grade)
  • Digital scales are critical
  • Receipts must be printed immediately
  • Offline operation is mandatory
  • Auditability and data privacy are non-negotiable

It runs on industrial Android POS devices with:

  • Built-in thermal printer
  • Barcode / QR scanner
  • Card or ID reader
  • Connection to digital weigh scales (RS-232, USB, Bluetooth)

Web Dashboard (Owner & Head Office)

Most businesses begin using the dashboard after the first few weeks of operation, or when scaling beyond a single POS device and needing a clear, consolidated view of performance.

SimpliPOSFlex includes an optional web dashboard designed for owners, managers, and head-office teams who need visibility without interfering with daily operations.

The dashboard is read-only by default and focuses on insight, control, and trust.

What the Dashboard Is Used For

  • Daily / Monthly Overview
    Total weight, total payout, transaction count, and trends across time

  • Material & Price Analysis
    See which materials drive volume and cost, and how pricing changes affect margins

  • Branch & Device Monitoring
    Compare performance across branches, yards, or POS devices

  • Supplier / Customer Statements
    View aggregated weight and payout history per supplier or partner

  • Audit & Exception Review
    Review voided tickets, manual price overrides, and supervisor approvals

What the Dashboard Does NOT Do

  • ❌ It does not control real-time POS operations
  • ❌ It does not change prices silently
  • ❌ It does not bypass on-site approval workflows

This separation prevents mistakes, abuse, and remote interference.

Privacy & Control by Design

  • Dashboard access is role-based (owner / auditor / manager)
  • All sensitive actions remain on the POS device
  • Data shown is encrypted during sync and storage
  • Dashboard can be self-hosted or disabled entirely

The dashboard exists to increase transparency, not to take control away from the operation.

AI Prediction & Fraud Detection (Privacy‑First)

SimpliPOSFlex includes optional AI-powered analytics designed to support owners and auditors — without compromising data privacy or on-site control.

AI features are assistive, not autonomous. The system never changes prices or blocks transactions automatically.

What AI Helps With

  • Anomaly Detection
    Identify unusual patterns such as abnormal weight entries, frequent manual overrides, repeated voids, or suspicious timing patterns

  • Fraud Risk Signals
    Highlight transactions that deviate from historical norms (per operator, per material, per time window)

  • Trend & Volume Prediction
    Forecast expected daily or weekly weight volume to support planning and cash-flow management

  • Price Sensitivity Insights
    Simulate how price changes may affect volume and payout (read-only analysis)

What AI Will NOT Do

  • ❌ It does not auto‑approve or auto‑reject transactions
  • ❌ It does not secretly monitor employees
  • ❌ It does not send data to third‑party AI services

Privacy‑First AI Design

  • AI runs on anonymized and aggregated data
  • Raw transaction data remains encrypted
  • Models can run on‑premise or self‑hosted
  • AI features are opt‑in per customer

AI exists to support human judgment, not replace it.



Hardware-Native by Design (Not an Add-On)

SimpliPOSFlex connects directly to real equipment.

Digital Weigh Scales

  • RS-232 (via USB or Bluetooth SPP)
  • USB (virtual COM / HID)
  • Stable-weight detection
  • Tare & deduction rules

Built-in Printers

  • Instant receipt printing
  • Custom ticket formats
  • QR codes for verification

Scanners & Cameras

  • Ticket lookup
  • Photo evidence
  • Fraud prevention

This is not “POS + integration later”.
Integration is the product.


Designed for Real-World Workflows

SimpliPOSFlex follows how people actually work on the floor:

  1. Place material on scale
  2. Weight is captured automatically
  3. Operator selects material & grade
  4. System calculates payout
  5. Supervisor approval (if needed)
  6. Receipt prints instantly

No spreadsheets.
No copy-paste.
No guessing.


Privacy Is Architecture, Not a Checkbox

Many businesses hesitate to digitize because they fear losing control of their data.

SimpliPOSFlex is built with privacy-first architecture:

  • Offline-first: works without internet
  • Encrypted local storage
  • Role-based access control
  • Immutable audit logs
  • Cloud sync is optional, not forced
  • Customer owns their data

We don’t sell data.
We don’t mine data.
We don’t lock you in.

Your operation data stays yours.


Who Is SimpliPOSFlex For?

SimpliPOSFlex is ideal for:

  • Recycle & scrap yards
  • Agricultural produce buying stations
  • Refill & bulk material shops
  • Pawn & precious metal businesses
  • Industrial receiving and warehouses

If your business depends on measurement + trust, SimpliPOSFlex fits.


Built as a Flexible Platform

SimpliPOSFlex is modular by design:

  • One core POS engine
  • Vertical-specific modules
  • Custom rules per business
  • Scales from single device to multi-branch operations

This allows us to start simple and grow with your operation.

Open‑Source Software Stack

For decision makers: This section explains the technology choices behind SimpliPOSFlex. In simple terms, using open‑source software means the system remains transparent, secure, adaptable, and under your control for the long term — without dependency on a single vendor or proprietary cloud.

SimpliPOSFlex is built entirely on open‑source technologies, ensuring transparency, auditability, and long‑term independence.

On‑Device (Android POS)

  • Android Open Source Project (AOSP) – Base operating system
  • Kotlin / Java – Native Android application
  • SQLite + SQLCipher – Encrypted local database
  • Android Keystore – Secure key storage
  • ESC/POS (open protocol) – Thermal printing
  • Bluetooth SPP / USB Serial (open specs) – Scale communication

Backend & Sync (Optional, Self‑Hosted)

  • Python – Core backend language
  • Django / Django REST Framework – API & business logic
  • PostgreSQL – Primary database
  • Redis – Caching & background jobs
  • Celery – Asynchronous task processing
  • Nginx – Reverse proxy

Infrastructure

  • Docker / Docker Compose – Deployment & isolation
  • Linux (Ubuntu / Debian) – Server OS
  • WireGuard – Secure device‑to‑server networking (optional)

Security & Privacy

  • AES‑256 / RSA / TLS – Industry‑standard cryptography
  • OpenSSL – Cryptographic primitives
  • Role‑Based Access Control (RBAC) – Implemented at application level

No proprietary cloud lock‑in. No closed protocols. Full control remains with the customer.

Why We Use an Open‑Source Stack

Factories and industrial businesses operate on long time horizons. Software choices must prioritize stability, control, and risk reduction, not short‑term convenience.

We choose an open‑source stack because:

  • Long‑term survivability – The system is not dependent on a single vendor’s business decisions. Even years later, it can be maintained, audited, or extended.
  • Auditability & trust – Open technologies make it possible to review security mechanisms, data handling, and compliance requirements transparently.
  • No vendor lock‑in – Customers are never forced into proprietary licenses, hidden dependencies, or sudden pricing changes.
  • On‑premise & private deployment – Open‑source enables local or private installations for factories that cannot rely on public cloud services.
  • Easier integration – Open standards integrate more safely with existing ERP, MES, accounting, and custom factory systems.

Open‑source is not an ideology. It is a practical choice for factories that value control, independence, and operational continuity.

System Architecture (Overview)

flowchart TB
    POS["Android POS Device
(SimpliPOSFlex App)"]
    Scale["Digital Weigh Scale
(RS-232 / USB / Bluetooth)"]
    Printer["Built-in Thermal Printer"]
    Scanner["Barcode / QR Scanner
Camera"]
    LocalDB["Encrypted Local DB
(SQLite + SQLCipher)"]
    Cloud["Optional Backend
(Django + PostgreSQL)"]
    Dashboard["Web Dashboard
(Owner / Head Office)"]

    Scale --> POS
    Scanner --> POS
    POS --> Printer
    POS --> LocalDB
    POS -. Optional Encrypted Sync .-> Cloud
    Cloud --> Dashboard

The system is designed to operate fully offline. Cloud synchronization is optional and encrypted end-to-end.

Pricing & Engagement Model

SimpliPOSFlex is priced to reflect real-world installation, hardware integration, and long-term reliability — not mass-market SaaS assumptions. Most customers begin with the simplest configuration and expand only as their operation grows.

Pricing Overview (Starting Price – English‑Speaking Markets)

Transparent starting prices for planning and budgeting. Final pricing may vary based on workflow complexity and local requirements.

Item Description Pricing Model Starting Price (USD)
Initial Setup & Deployment Workflow study, POS configuration, scale integration, receipt format setup, remote onboarding One-time from $1,500
POS Device License SimpliPOSFlex license per Android POS device Monthly from $49 / device
Optional Cloud Dashboard Secure backend, encrypted sync, web dashboard access Monthly from $99 / org
AI Prediction & Fraud Detection Anomaly detection, trend prediction, audit insights (opt-in) Monthly from $79 / org
Customization / Integration Custom reports, vertical rules, accounting or ERP integration Project-based Quoted

What the Pricing Includes

  • Offline-first POS operation
  • Encrypted local data storage
  • Hardware integration (scale, printer, scanner)
  • Regular software updates
  • Privacy-first architecture (no data resale)

What Is Intentionally Separate

  • POS hardware (device, scale, accessories)
  • Internet connectivity
  • Major workflow changes after go-live

This pricing model ensures sustainability, proper support, and long-term partnership — not shortcut deployments.


Example Cost Breakdown

To make planning easier, below are typical cost examples for English-speaking markets. These are illustrative scenarios based on common deployments.

Example 1: Single-Site Operation (1 POS Device)

First Year

Cost Item Amount (USD)
Initial Setup & Deployment $1,500
POS Device License ($49 × 12 months) $588
Optional Cloud Dashboard ($99 × 12 months) $1,188
Estimated First-Year Total $3,276

Following Years (Maintenance & Subscription)

Cost Item Annual Cost (USD)
POS Device License $588
Cloud Dashboard $1,188
Estimated Annual Ongoing Cost $1,776 / year

Example 2: Small Multi-Device Site (3 POS Devices)

First Year

Cost Item Amount (USD)
Initial Setup & Deployment $1,500
POS Device Licenses ($49 × 3 × 12 months) $1,764
Optional Cloud Dashboard ($99 × 12 months) $1,188
Estimated First-Year Total $4,452

Following Years (Maintenance & Subscription)

Cost Item Annual Cost (USD)
POS Device Licenses $1,764
Cloud Dashboard $1,188
Estimated Annual Ongoing Cost $2,952 / year

AI analytics, custom integrations, and on-site support are optional add-ons and quoted separately based on requirements.


Why We Built SimpliPOSFlex

We’ve seen too many businesses forced to adapt their workflow to software that wasn’t built for them.

SimpliPOSFlex does the opposite.

We adapt the software to your reality.


Let’s Talk

If you operate a specialized business — or plan to digitize one —
we’re happy to observe your workflow, design the right setup, and build it properly.

📧 Contact: hello@simplico.net
🌐 Website: https://www.simplico.net