Kuntek CEO: AI Agent Security Must Connect the Full Lifecycle to Reduce Response Time
South Korean convergence-security firm Kuntek CEO Bang Hyuk-jun argues that securing AI agents requires connecting asset identification (extending software bill-of-materials to an AI-BOM), runtime policy enforcement, and hardware-isolated data protection into one measurable lifecycle, rather than treating them as separate products.
When enterprises deploy AI agents, the first question is not which threat to block but what actually exists in the environment. Bang Hyuk-jun, CEO of South Korean convergence-security company Kuntek, stated in a November 2026 interview with Byline Network that AI agent security must begin from the same principle as traditional security: asset visibility. He noted that if an organization cannot accurately identify the servers and software it already holds, managing AI agent risk becomes more difficult still—because knowing which systems are affected is a prerequisite for finding vulnerabilities and responding to them.
Kuntek extends this identification into three layers. First, a software bill-of-materials (SBOM) catalogs the programs, libraries, and versions inside each software package; when a vulnerability is disclosed in a component, the SBOM helps trace which systems are affected. Second, an operational bill-of-materials (OBOM) checks what is actually running in live environments, not just what was declared at build time. Third, an AI bill-of-materials (AI-BOM) records which models are in use, where they came from, what licenses they carry, and what tools and permissions agents have connected to. Bang called this raising the "resolution of visibility" across the AI lifecycle. Kuntek's supply-chain product AEZIZ, according to the company, has expanded its SBOM management into the AI-BOM domain, adding checks for model provenance, dangerous file formats, and agent-connected tool permissions.
Identification alone does not eliminate runtime risk. Bang pointed to indirect prompt injection—where malicious instructions are hidden in documents an agent reads—as a concrete failure mode. A hiring AI that interprets hidden text in a resume as a legitimate work command could produce distorted evaluations. He noted that even when an agent uses a normal account and API, it can still perform a dangerous action; existing authentication and network access controls alone make it difficult to judge whether the agent's behavior matches its business purpose. Kuntek's answer is a platform called ASH, which checks each agent action against security policy before execution: if an agent attempts to send customer data to an external system, the platform verifies the purpose and permissions of that tool call, then allows, blocks, or escalates to human approval. The company describes ASH as being in proof-of-concept and early commercialization.