AI Governance · Security Governance · Technology Risk
Fixing what to decide, who is responsible, how far work is delegated and where people review it — through to the conditions under which implementation and operation can continue.
For IT, information security, risk, and corporate-planning teams
Fragment Practice is an independent advisory practice for issues involving AI, security, and technology risk. It separates the issues, clarifies what must be decided and who is responsible, and develops requirements and briefing material. No finished brief is required.
Founder Yasuhiro Shinsho worked across systems development, IT risk, security, and cloud and AI risk assessment at BIPROGY, KPMG Consulting, and Nomura Research Institute / NRI Secure Technologies before going independent.
Services covers organization-specific work done with you. Products offer reusable, self-guided methods. Writing shares generalized ideas, frameworks, and ways of framing problems.
What you can bring
Start from the one closest to where you are. Each links to what gets organised and what material remains.
AI governance
How far generative AI may be used, and on whose approval. The checks and records for each use, and the criteria for approval and exceptions, organised.
Security governance
Security guidelines and internal rules, and what customers or a parent company ask of you, organised into requirements and review points that can be checked in practice.
Also within this scene: How to respond, as a company, to an external scheme or standard / Decisions and roles when an incident or outage stops systems (IT continuity)
Technology risk
A platform or service concept, the requirements you give vendors, or a proposal or policy you already have — put into a form you can compare and decide on. Independent review is part of this: it returns findings and open questions, not a verdict, a score, or a maturity level, and it does not stand in for audit, assurance, or certification.
Explaining the work to management and stakeholders runs through every scene; where it is needed, the work includes that brief.
Examples
Shown by sector or former employer, without client names or confidential detail.
Financial institution
Organised, use by use, the information handled, how output is used, human review, and approval and records — and combined system controls with rule-based operation into one approach to control.
Systems integrator
Compared product-led, platform-extension and AI-SOC models, evaluated on cost acceptability, operational transparency, speed to launch, staged scalability, and low dependence on any one vendor.
KPMG Consulting (the founder's prior role)
Worked on IT business-continuity planning, incident-response readiness with the design and running of exercises, and the standardisation of supplier security assessment.
Nomura Research Institute / NRI Secure Technologies (the founder's prior role)
In third-party and risk assessment of a cloud AI platform, organised the evaluation points — permissions, logging, data protection, whether data is used for external training. In a device-platform renewal, structured requirements that connected the technical design to security needs.
Ways to work together
Structuring requirements, comparing options, reviewing independently, and designing who decides and who approves — including where implementation is already under way. Start small: you do not need to pick the final shape before the first conversation.
Focused first step
From ¥300,000
Excl. tax · 1–2 sessions
When the issue is real but you cannot yet say what to decide.
One or two sessions to separate the situation, name the decisions, set priorities, and choose the next move.
Bounded sprint
From ¥1,200,000
Excl. tax · 2–6 weeks
When a meeting, report, rule update, or handoff needs material soon.
Research, structuring, review, and drafting that leave decisions, options, risks, open questions, and responsibility ready to use.
Scoped advisory
From ¥600,000 / month
Excl. tax · Monthly or biweekly cadence
When important decisions keep coming and you want an expert at the key points.
A defined cadence with agreed themes, review scope, and response expectations — without a resident PMO or daily operations.
Founder
Yasuhiro Shinsho worked on systems development, vulnerability assessment, and CSIRT at BIPROGY; IT risk, IT continuity, and incident response at KPMG Consulting; and security advisory with cloud and AI risk assessment at Nomura Research Institute / NRI Secure Technologies. He became independent in October 2025. Having worked on both the technical side and the risk and governance side, he handles technology questions and control questions together rather than apart.
Practice notes
Notes drawn from practice and written for broader use. They offer a direct view of how problems are framed here and can be read or shared on their own.
Jul 2026
AI governance should not be treated as a fixed policy document. As AI products, usage patterns, and organizational conditions change, organizations need a review cycle that updates decision criteria, review points, responsibility boundaries, and handoff material.
Jul 2026
Security product decisions depend on more than technical performance and price. This Practice Note examines how existing product environments, licensing structures, the ability to explain the selection, operating burden, and responsibility boundaries shape the decision friction around integrated and specialized security products.
Jun 2026
A meeting can look productive while the work itself has not moved to its next state. This Practice Note explains how to define outcome conditions before a meeting so decisions, review points, responsibility boundaries, and handoff material remain after the conversation.
Next step
Your current situation, and what has to be decided by when, is enough. The first reply covers which shape is likely to fit. To structure it yourselves first, Products holds reusable working material.
