
Sign up to save your podcasts
Or


As AI becomes part of daily work,
questions like these often appear:
In this episode, we explore accountability,
an important concept in AIMS (AI Management Systems).
Accountability does not mean legal language.
It simply means:
👉 Being clear about who takes responsibility.
When these points are clear,
AI can be used more safely and confidently.
This episode follows the previous topic of transparency
and helps you move from
“being able to explain AI use”
to
“being ready to take responsibility for AI use.”
If you want to use AI in a healthy and sustainable way,
this episode is for you.
Many people working in IT or administration feel this challenge:
“I understand the importance of information security,
but top management doesn’t seem very interested.”
In this episode, we talk about how to involve executives in information security,
from a practical, real-world perspective.
This is not about explaining detailed rules or standards.
Instead, we focus on how to speak in the language of management:
Rather than “convincing” management,
this episode shares tips on thinking together and creating a shared sense of responsibility.
If you struggle with explaining ISMS, P-Mark, or security initiatives to executives,
this episode will give you helpful hints.
As AI becomes more common in the workplace,
questions like these often come up:
“Was this created by AI?”
“How much should we explain?”
In this episode, we explore transparency,
a key concept in AIMS (AI Management Systems),
from a practical, real-world perspective.
Transparency does not mean technical explanations.
It simply means being able to explain how AI is used.
Being clear about these points builds trust
both inside and outside the organization.
This episode is especially helpful if you are thinking about
how to explain AI usage after setting internal AI rules.
“Can one IT person really handle ISMS or the Privacy Mark?”
This is a very common question.
In this episode,
I talk about this issue from a key risk perspective: over-reliance on one person.
You’ll hear about:
Why running security certification alone is risky
What actually happens when knowledge stays with one person
How to build a more sustainable, shared security setup
Information security is not something one person should carry alone.
It works best when responsibilities are shared across the organization,
not concentrated in one individual.
This episode is especially helpful if:
You are the only IT or security person in your company
You are worried about handover, continuity, or burnout
You want a realistic way to run ISMS or Privacy Mark operations
Security is important —
but explaining it to management is often the hardest part.
In this episode,
I talk about how to communicate information security
in a way that actually makes sense to executives.
We cover:
This episode is for anyone who feels
“stuck in the middle” between the field and management.
AI is becoming part of everyday work.
But many people feel unsure and think:
“AI is useful, but is it really safe to use this way?”
In this episode,
I explain what AIMS (AI Management System) is
in a simple and practical way.
You’ll learn:
AIMS is not about restricting AI.
It is about creating clear rules and shared responsibility
so AI can be used with confidence.
This episode is a beginner-friendly introduction
for anyone who is starting to think about AI governance
or company-wide AI rules.
Many companies think about security certifications like ISMS or the Privacy Mark and wonder:
“Isn’t this still too early for a company our size?”
In this episode, Yoshida shares a practical, real-world perspective on that question.
Instead of focusing on certification requirements,
this episode explores:
This is not about forcing certification.
It’s about thinking early, calmly, and realistically
so security doesn’t become a last-minute crisis.
If you’re unsure when to start thinking about ISMS or security governance,
this episode is for you.
As AI use grows inside companies, many people start asking:
“Do we need internal AI rules?”
“But where should we even start?”
In this episode, we build on the previous discussion about making AI risks visible,
and focus on the next step:
how to turn those risks into simple, practical internal AI rules.
This is not about creating long or strict policies.
Instead, we talk about a realistic approach for small and mid-sized companies:
Using the AIMS (AI Management System) mindset as a reference,
this episode explains how to create “rules that help people act,” not rules that stop them.
If you are involved in AI usage, internal controls, or information security,
and feel unsure about AI rules, this episode is for you.
Key message:
Perfect rules are not necessary. Practical rules are.
What actually changes in a company after getting ISMS, the Privacy Mark, or PIMS?
In this episode, I talk about the real changes that happen after certification,
based on practical experience with ISMS, the Privacy Mark, and PIMS (ISO/IEC 27701).
Getting certified does not suddenly change everything overnight.
But over time, clear and meaningful changes begin to appear.
For example:
Instead of listing theoretical benefits,
this episode focuses on what really changes in daily operations and culture.
If you are thinking about certification,
or already running ISMS, the Privacy Mark, or PIMS,
this episode will help you understand what comes after getting certified.
in this episode,
we talk about how to make AI risks visible in daily work.
Many people use AI tools like ChatGPT or Copilot at work,
but often feel unsure:
In this episode,
we explain AI risk in a simple and practical way,
from an information security point of view.
You will learn:
We also introduce the basic idea of AIMS (ISO/IEC 42001)
and why “visibility” is important for safe AI use.
This podcast is for small and mid-sized companies,
and for anyone who wants to use AI with confidence, not fear.
No technical knowledge is required.
Let’s take the first step toward safe and responsible AI use—together.
From the publisher's feed