CYBERSECURITY ASSESSMENT, THREAT INTELLIGENCE & SECURE ENGINEERINGTOKYO — EST. 2022

Verify, Defend,and Engineer the Next Era.

PILLAR 01 — SECURITY SERVICES (DEFENSIVE ASSESSMENT & THREAT RESEARCH)

Vulnerability Assessment / Penetration Testing / Exploit Verification / Malware Analysis / Threat Intelligence / AI Security

PILLAR 02 — SECURE ENGINEERING (SECURITY-FIRST SYSTEM DEVELOPMENT)

Web & Mobile Applications / Enterprise Core Systems / Cloud-Native Infrastructure

FIG. 01 — AUTHORIZED VERIFICATION & DEFENSE-IN-DEPTH ARCHITECTUREGATE 01 / ROE SCOPEGATE 02 / ZERO TRUSTGATE 03 / KMS VAULTAUTHORIZED VERIFICATIONWSTG / PTESIAM / RLSPROTECTED ASSET

JOS LLC (jos) is a Tokyo-based cybersecurity and systems engineering firm dedicated to defensive security. From explicitly authorized vulnerability assessments, penetration testing, and multilingual threat intelligence to threat-modeled application and cloud engineering, we help organizations verify and harden critical systems from design through operation.

01AboutDefensive Cybersecurity & Engineering

Rigorous Security Verification Meets Disciplined Engineering.

Protecting modern infrastructure requires two complementary capabilities: the analytical precision to identify how systems fail under adversarial conditions, and the engineering discipline to build architectures that prevent those failures by design. JOS LLC was founded in Tokyo to unite both disciplines under one roof.

Our primary business is defensive cybersecurity—helping organizations identify, validate, and remediate security risks—alongside secure software and cloud engineering. All offensive security testing, exploit verification, and malware analysis conducted by JOS LLC strictly comply with Japan’s Act on Prohibition of Unauthorized Computer Access and applicable laws, and are performed exclusively on systems we own or under explicit prior written authorization (Rules of Engagement) from the asset owner.

I

Strictly Authorized Scope (Authorized Only)

We never conduct vulnerability scanning, penetration testing, or exploit validation without prior written authorization from the system owner. Every engagement operates within a mutually signed Rules of Engagement (RoE) defining exact targets, time windows, and escalation channels.

II

Direct Principal Engagement

We do not use sales intermediaries or multi-layered subcontracting. The security researchers and principal engineers who scope your engagement are the same professionals who execute the assessment, verify patches, and write production code.

III

Verifiable, Reproducible Outcomes

In security assessments, we deliver clear proof-of-concept evidence and actionable remediation code rather than generic scanner output. In engineering engagements, we codify infrastructure (IaC) and document Architecture Decision Records (ADRs) for long-term operational resilience.

02Security ServicesDefensive Verification & Threat Defense

Authorized Verification Across Every Layer of Your Stack.

We provide seven specialized defensive security services spanning web and mobile applications, cloud infrastructure, AI/LLM systems, incident response, and threat intelligence. Every engagement is governed by strict written authorization and data protection controls.

02-1OWASP WSTG / ASVS / CIS Benchmarks

Vulnerability Assessment (Web, API, Mobile & Cloud Configuration)

OVERVIEW

Systematic identification and risk prioritization of architectural, implementation, and configuration vulnerabilities across web applications, APIs, mobile apps, and cloud environments.

TARGET ASSETS

Web applications, REST / GraphQL / gRPC APIs, iOS and Android applications, and AWS / GCP cloud configurations (IAM policies, network boundaries, storage permissions).

METHODOLOGY & STANDARDS

Manual expert review combined with targeted tooling aligned with OWASP Web Security Testing Guide (WSTG), OWASP Application Security Verification Standard (ASVS), OWASP API Security Top 10, and CIS Benchmarks.

DELIVERABLES

Comprehensive Vulnerability Assessment Report (executive summary, CVSS severity ratings, step-by-step reproduction evidence, and concrete code/configuration remediation examples) plus a post-remediation verification report.

Conditions of Engagement
1. Prior Written Authorization (Rules of Engagement)

Testing commences only after executing a formal agreement and written Rules of Engagement specifying authorized hosts, URIs, testing windows, and permitted techniques.

2. Strict Non-Contact Outside Scope

We never probe, scan, or interact with systems, endpoints, or third-party assets outside the explicitly agreed scope.

3. Client Data Handling

All captured traffic logs, screenshots, and diagnostic artifacts are encrypted in transit and at rest, and are permanently deleted within 30 days of final deliverable acceptance in accordance with our Client Data Handling Policy.

02-2PTES / NIST SP 800-115 / MITRE ATT&CK

Penetration Testing (External, Internal & Cloud)

OVERVIEW

Scenario-driven adversarial simulation evaluating whether chained vulnerabilities could allow an attacker to breach perimeter defenses, escalate privileges, move laterally, or reach high-value assets—while testing the effectiveness of detection and response controls.

TARGET ASSETS

Internet-facing perimeters (External Penetration Testing), internal corporate or production networks (Internal Penetration Testing), and cloud-native environments (IAM role chains, container clusters, service meshes).

METHODOLOGY & STANDARDS

Goal-oriented testing aligned with PTES (Penetration Testing Execution Standard), NIST SP 800-115, and the MITRE ATT&CK framework.

DELIVERABLES

Penetration Testing Report detailing attack path narratives, defensive control and alerting evaluation, attack timeline, and prioritized architectural remediation roadmap.

Conditions of Engagement
1. Prior Written Authorization (Rules of Engagement)

Formal written sign-off on test objectives, prohibited actions (such as denial-of-service), emergency stop procedures, and real-time point-of-contact channels.

2. Strict Non-Contact Outside Scope

Testing is strictly confined to authorized IP ranges, accounts, and cloud projects; out-of-scope systems and neighboring tenants are never touched.

3. Client Data Handling

Privilege or data access is demonstrated using benign markers or metadata verification rather than exfiltrating real customer PII or confidential records. All raw testing artifacts are deleted within 30 days of report delivery.

02-3Isolated Lab Reproduction & Remediation Verification

Exploit Verification & Proof-of-Concept (PoC) Development

OVERVIEW

Technical validation of newly disclosed CVEs or complex software defects to determine real-world exploitability within a client’s specific architecture, assess blast radius, and verify the efficacy of patches or compensating controls.

TARGET ASSETS

Software, middleware, custom modules, and staging environments owned by the client or explicitly authorized in writing for testing.

METHODOLOGY & STANDARDS

Reproduction and impact evaluation conducted strictly within JOS-managed isolated environments logically separated from client production networks, with outbound traffic restricted to an allow-list and logged (or within client-designated staging environments), followed by remediation verification to confirm that patches or WAF rules completely neutralize the exploit path.

DELIVERABLES

Technical Verification Report including root-cause analysis, benign/defanged Proof-of-Concept (PoC) scripts for internal patch testing, impact assessment, temporary mitigation rules, and patch verification results.

Conditions of Engagement
1. Prior Written Authorization (Rules of Engagement)

Written confirmation of asset ownership/licensing rights and explicit restriction of use to defensive validation and patch verification.

2. Strict Non-Contact Outside Scope

Exploit reproduction is executed in JOS-managed isolated environments logically separated from client production networks, with outbound traffic restricted to an allow-list and logged, without touching unapproved production networks or external third-party systems.

3. Client Data Handling

Synthetic data is used during reproduction. Any client-supplied binaries or configuration files are stored in encrypted storage and permanently purged within 30 days after final delivery.

02-4Static / Dynamic Analysis, IOC Extraction & Triage

Malware Analysis & Incident Response Support

OVERVIEW

Rapid technical investigation of suspicious binaries, scripts, and compromised hosts to determine malware capabilities, command-and-control (C2) behavior, and intrusion root causes, supporting containment and recovery.

TARGET ASSETS

Suspicious executables, scripts, document samples, memory dumps, and system/cloud audit logs from suspected security incidents.

METHODOLOGY & STANDARDS

Static and dynamic analysis performed inside JOS-managed isolated environments logically separated from client production networks, with outbound traffic restricted to an allow-list and logged (isolated sandboxes), extraction of Indicators of Compromise (IOCs), behavioral mapping against MITRE ATT&CK, and triage guidance aligned with NIST SP 800-61.

DELIVERABLES

Malware Analysis Report (sample capabilities, persistence mechanisms, C2 protocol breakdown), actionable IOC packages (YARA rules, file hashes, network indicators), and containment/hardening recommendations.

Conditions of Engagement
1. Prior Written Authorization (Rules of Engagement)

Conducted under a signed non-disclosure and incident support agreement authorized by the legal owner or custodian of the affected systems.

2. Strict Non-Contact Outside Scope

Dynamic execution occurs exclusively within JOS-managed isolated environments logically separated from client production networks, with outbound traffic restricted to an allow-list and logged, preventing any contact with external C2 servers or third-party networks.

3. Client Data Handling

Submitted malware samples, forensic images, and logs are handled in encrypted, access-controlled storage and permanently destroyed within 30 days of engagement completion.

02-5Multilingual OSINT (incl. Chinese-Language Sources) & Briefings

Threat Intelligence & Multilingual OSINT

OVERVIEW

Collection and analysis of emerging threat campaigns, vulnerability exploitation trends, and supply-chain risks tailored to your industry and technology stack to support proactive defense.

TARGET ASSETS

Enterprise CSIRT/SOC teams, engineering leadership, and executive decision-makers.

METHODOLOGY & STANDARDS

Multilingual OSINT (Open-Source Intelligence) covering English, Japanese, and Chinese-language sources, structured analysis of sector-specific threat trends, vulnerability intelligence triage, and executive briefings translating technical threat data into strategic risk decisions. All collection is strictly limited to lawful open sources and licensed feeds.

DELIVERABLES

Tailored Threat Intelligence Reports, prioritized defensive action advisories, and executive-level threat briefings.

Conditions of Engagement
1. Prior Written Authorization (Rules of Engagement)

Written agreement defining monitored brand domains, technology profiles, and intelligence reporting cadence.

2. Strict Non-Contact Outside Scope

Research is strictly passive and lawful; we never perform unauthorized active scanning against third parties, engage in deceptive elicitation, or purchase illicitly obtained data.

3. Client Data Handling

Client asset inventories and internal context shared for intelligence tailoring are encrypted and deleted within 30 days of contract completion.

02-6OWASP Top 10 for LLM Applications & AI Governance

AI Security (LLM Application Assessment & Governance)

OVERVIEW

Specialized security assessment and architectural hardening for applications powered by Large Language Models (LLMs), Retrieval-Augmented Generation (RAG), and autonomous AI agents.

TARGET ASSETS

Customer-facing and internal LLM applications, RAG pipelines, agentic workflows with tool/API execution, and enterprise AI platforms.

METHODOLOGY & STANDARDS

Comprehensive testing aligned with the OWASP Top 10 for LLM Applications, evaluating direct and indirect prompt injection, sensitive data leakage (system prompt extraction, cross-tenant RAG leakage), privilege escalation and excessive agency via tool/function calling, and insecure output handling—combined with AI governance and guardrail design support.

DELIVERABLES

AI Security Assessment Report (test cases, transcript evidence, severity ratings, input/output guardrail architectures, and RAG permission-boundary designs) and Enterprise AI Security Guidelines.

Conditions of Engagement
1. Prior Written Authorization (Rules of Engagement)

Written authorization covering target AI endpoints, connected data stores, and compliance with underlying foundation model provider policies.

2. Strict Non-Contact Outside Scope

Testing is restricted to designated staging or authorized tenant endpoints without impacting shared multi-tenant infrastructure or external third-party APIs.

3. Client Data Handling

Assessment prompts and model outputs are handled under the foundation model provider's commercial terms, which exclude use for model training, and permanently deleted within 30 days of report delivery.

02-7STRIDE Threat Modeling, Zero Trust & Observability

Security Architecture & SRE Design

OVERVIEW

Embedding threat modeling, zero-trust access boundaries, cryptographic key management, and observability directly into the blueprint of new and modernized systems.

TARGET ASSETS

New web and SaaS platforms, enterprise system modernizations, cloud migrations, and high-reliability production infrastructure.

METHODOLOGY & STANDARDS

STRIDE threat modeling, OWASP ASVS, NIST SP 800-207 (Zero Trust Architecture), KMS envelope encryption, OpenTelemetry immutable audit logging, and automated CI/CD security guardrails (SAST, SCA, IaC scanning).

DELIVERABLES

Data Flow Diagrams (DFDs) and Threat Models, Architecture Decision Records (ADRs) for authentication and authorization boundaries, hardened Terraform IaC modules, and incident response runbooks.

Conditions of Engagement
1. Prior Written Authorization (Rules of Engagement)

Formal agreement on architectural scope, protected asset classifications, and target compliance baselines.

2. Strict Non-Contact Outside Scope

Reviews of existing environments use read-only credentials or exported configuration manifests; no production changes occur outside approved change-management windows.

3. Client Data Handling

All architectural diagrams, schemas, and configuration files received during design reviews are encrypted and deleted within 30 days of project completion.

03EngineeringSecurity-First System Development

Software and Cloud Infrastructure Built by a Security Firm.

Insights gained from defensive security assessments directly inform how we build software. We engineer systems across three core domains where security, maintainability, and operational clarity are built in from Day One.

01Type-Safe Frontend, API & Mobile

Web & Mobile Application Engineering

From mission-critical business applications to iOS and Android apps, we build software with strict type safety, OAuth 2.1 / Passkey authentication, and hardened security headers by default.

CORE STACK & ARCHITECTURE
  • Next.js / React / TypeScript
  • Go / Rust / Node.js / Python
  • iOS / Android
02Legacy Modernization & Data Pipelines

Enterprise & Core Systems

Modernizing legacy systems, building ETL data pipelines, and integrating SaaS platforms with explicit domain boundaries, database-level tenant isolation (Row-Level Security), and tamper-evident audit trails.

CORE STACK & ARCHITECTURE
  • Legacy Modernization / Domain-Driven Boundaries
  • Data Pipelines
  • PostgreSQL RLS
03Reproducible Cloud & Observability

Cloud-Native Infrastructure

Designing reproducible AWS and GCP environments managed via Terraform, featuring isolated network topologies, least-privilege IAM, Kubernetes orchestration, OpenTelemetry observability, and FinOps cost governance.

CORE STACK & ARCHITECTURE
  • AWS / GCP
  • Terraform · Kubernetes · Docker
  • Cloudflare
04PrinciplesCore Doctrine

Start from Defense.

We embed threat modeling, cryptographic verification, and legal compliance into every phase of assessment, design, development, and operation. These seven principles govern all work at JOS LLC.

  1. 01STRIDE / Threat Modeling

    Begin with threat modeling during design to clarify protected assets and assumptions.

    Before writing code, we map Data Flow Diagrams (DFDs) and trust boundaries to identify and eliminate architectural weaknesses on the drawing board.

  2. 02OAuth 2.1 / RBAC · ABAC

    Agree on and document authentication, authorization, and data boundaries before writing code.

    Access matrices and tenant isolation rules are formally documented as Architecture Decision Records (ADRs) prior to implementation.

  3. 03AWS & GCP KMS / Workload Identity

    Keep secrets and cryptographic keys out of code using KMS and least-privilege IAM.

    We prohibit static plaintext credentials in repositories or environment files, enforcing short-lived OIDC Workload Identity tokens and KMS envelope encryption.

  4. 04Automated DevSecOps

    Run continuous SAST, SCA, and IaC scans in CI to detect drift and vulnerabilities early.

    Every commit is automatically evaluated for static code flaws, vulnerable dependencies, and infrastructure misconfigurations before deployment.

  5. 05OpenTelemetry / Audit Trail

    Ship audit logs, observability metrics, and incident runbooks alongside the initial release.

    Systems launch with tamper-evident audit logging, distributed tracing, and actionable incident response runbooks ready on Day One.

  6. 06Blameless Postmortem

    Cultivate a blameless learning culture that converts incident insights into structural safeguards.

    We treat incidents and findings as opportunities to strengthen systemic guardrails and automated regression tests rather than relying on individual vigilance.

  7. 07Rules of Engagement & Legal Compliance

    Authorized Only: We conduct all offensive security testing strictly within agreed scopes and with explicit permission from the asset owner.

    Every vulnerability assessment, penetration test, and exploit verification engagement complies with the Act on Prohibition of Unauthorized Computer Access and applicable laws, operating exclusively on JOS-owned environments or under prior written authorization from the system owner.

Architectural Specification Comparison

ARCHITECTURAL DIFFERENCE
Architecture Layer
Conventional Outsourced Development
JOS LLC Standard Baseline
Authentication & Access Boundary
Long-lived static tokens and application-layer-only permission checks
OAuth 2.1 / Passkey, short-lived tokens, and dual enforcement down to database Row-Level Security (RLS)
Data Protection & Cryptography
Disk-level encryption only, or static keys stored in plaintext environment variables
Per-record / per-tenant KMS envelope encryption with immediate in-memory key zeroization
Infrastructure & Supply Chain
Manual console changes and one-off security checks right before launch
Reproducible Terraform IaC, continuous SAST/SCA/IaC checks in CI, and signed container deployments
Audit Trails & Observability
Ad-hoc log inspection on production servers after an incident occurs
Tamper-evident structured audit logs, OpenTelemetry distributed tracing, and pre-defined SRE runbooks
05ProcessExecution Workflows

Structured Execution. Explicit Authorization.

Whether conducting an authorized security assessment or building a new software system, we follow transparent workflows with clear documentation at every gate.

TRACK A

Security Assessment Workflow (Scoping to Re-test)

01

Scoping & AuthorizationRules of Engagement

Define target assets, testing windows, permitted methodologies, exclusions, and emergency contacts in a mutually signed Rules of Engagement (RoE).

DELIVERABLES
  • Scope Definition
  • Signed Rules of Engagement (RoE)
02

AssessmentAuthorized Execution

Execute manual and tool-assisted verification strictly within the authorized scope and schedule, providing immediate notification if critical vulnerabilities are discovered.

DELIVERABLES
  • Status Updates
  • Critical Finding Advisories
03

ReportingEncrypted Deliverable

Deliver an encrypted report detailing CVSS severity ratings, reproduction steps, root causes, and concrete remediation code/configuration examples, followed by a debrief session.

DELIVERABLES
  • Encrypted Assessment Report
  • Executive Debrief
04

Remediation SupportEngineering Guidance

Collaborate directly with your engineering team to review proposed fixes, architectural adjustments, and compensating controls.

DELIVERABLES
  • Remediation Design Review
  • Technical Q&A
05

Re-testVerification & Data Purge

Verify that all remediations effectively resolve the identified issues without introducing regressions, issue the final verification report, and purge raw assessment data within 30 days.

DELIVERABLES
  • Re-test Verification Report
  • Raw Data Purge Confirmation
TRACK B

Secure Engineering Workflow (Discover to Operate)

01

DiscoverProblem & Asset Discovery

Deconstruct business workflows and existing systems to identify core assets, trust boundaries, and the exact problem to solve.

DELIVERABLES
  • Workflow & Problem Map
  • Asset & Risk Definition
02

DesignArchitecture & Boundaries

Establish information architecture, system topology, UI, and security controls in writing before implementation begins.

DELIVERABLES
  • Architecture Decision Records (ADR)
  • AuthZ & Data Boundary Specs
03

BuildDisciplined Implementation

Iterate through small releases backed by automated testing, continuous security scanning, and rigorous peer code review.

DELIVERABLES
  • Type-Safe Production Code & IaC
  • Automated Test Suites
04

OperateContinuous Operations

Support long-term reliability through continuous observability, security monitoring, vulnerability triage, and cost optimization.

DELIVERABLES
  • Telemetry Dashboards & Audit Logs
  • SRE Runbooks
06CompanyCorporate Profile & Registration

Corporate Information

Legal Name
JOS LLCJapanese Registered Name: JOS合同会社
Corporate Number
8010403028497Company Registration Number: 0104-03-028497
Established
September 8, 20222022年9月8日
Representative
Takuya Murata, Representative Member & CEO代表社員 村田 卓也
Registered Office
#102 Brighton Hills Tsunashimaen, 1-1-6 Nakaikegami, Ota-ku, Tokyo 146-0081, Japan〒146-0081 東京都大田区仲池上一丁目1番6号 ブライトンヒルズ綱島園102号
Business Activities
Security Assessment & Penetration Testing / Threat Intelligence / Incident Response Support / Secure System Development / Cloud Infrastructure Engineering / Security Architecture & Operations
Core Technologies
TypeScript · Go · Rust · Python · Next.js · React · AWS · GCP · Terraform · Kubernetes · PostgreSQL · Cloudflare
Contact Channels
General Inquiries: info@josforge.comSecurity, Vulnerability Reports & Urgent Matters: security@josforge.com
Meetings
Available both in-person (Tokyo) and online
TECHNOLOGY STACKCore Technologies Used in Production
TypeScript
Go
Rust
Python
Next.js
React
Node.js
NestJS
FastAPI
PostgreSQL
Terraform
Kubernetes
Docker
Google Cloud
Cloudflare
GitHub
07ContactCommunication Channels

Start a Conversation.

Whether you need an authorized security assessment, AI security review, or secure system architecture, our engineers review all inquiries directly and respond within 48 hours. Please select the appropriate channel below.

CHANNEL 01 — GENERAL & PROJECT INQUIRIES

Scoping and quotes for vulnerability assessments, penetration testing, AI security evaluations, secure software/cloud development, and general business inquiries.

Response Target: Within 48 hours
info@josforge.com
CHANNEL 02 — SECURITY DESK, RESPONSIBLE DISCLOSURE & URGENT

Urgent incident response or malware analysis requests, security posture inquiries from business partners, and vulnerability reports regarding JOS-operated services (Responsible Disclosure).

Response Target: Priority review within 48 hours (Vulnerability reports acknowledged within 3 business days)
security@josforge.com