[{"data":1,"prerenderedAt":1248},["ShallowReactive",2],{"article-\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule":3,"article-series-m365-copilot":1203},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"date":10,"category":11,"series":12,"seriesNo":13,"seriesLabel":14,"author":15,"thumbnail":16,"tags":17,"faq":23,"body":36,"_type":1197,"_id":1198,"_source":1199,"_file":1200,"_stem":1201,"_extension":1202},"\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule","articles",false,"","システム開発を外注するときのAI利用ルール｜開発会社に求める5つの約束と秘密情報の扱い","外注先のエンジニアは、Claude Code や Cursor などのAIツールに自社のコードや仕様書を読ませて開発しています。禁止ではなく条件を決めて約束してもらうための、開発会社に求める5つの必須事項と発注側のチェックリストを解説します。","2026-10-16","M365 Copilot導入","m365-copilot",5.2,"第5回（後編）","K.S.ロジャース株式会社","\u002Fimg\u002Fcontents\u002Fnews\u002Fthumb133.jpg",[18,19,20,21,22],"生成AI ガイドライン","AIガバナンス","システム開発","外注","Claude Code",[24,27,30,33],{"q":25,"a":26},"開発を外注するとき、開発会社のAIツール利用を禁止すべきですか？","禁止はおすすめしません。AIツールは開発の速さと品質に大きく影響するため、禁止すると開発会社の生産性が下がるか、ルールが守られなくなります。使ってよいツール、読ませてはいけない情報、成果物のレビュー方法などの条件を決め、開発会社に約束してもらう形が現実的です。",{"q":28,"a":29},"開発会社にAI利用について何を約束してもらえばよいですか？","最低限、①自社のリポジトリに外部連携アプリを入れるときは事前に合意する、②AIツールの利用は承認済みのものに限る、③秘密情報をプロンプトやログに載せない、④AIが作った成果物は人がレビューしてからマージする、⑤入力内容がAIの学習に使われない設定で使う、の5つです。",{"q":31,"a":32},"AIツールに読ませてはいけない情報は何ですか？","最も厳しく扱うべきなのは、パスワード・APIキー・トークン・秘密鍵などの認証情報で、一部を伏せた形でも入力しません。会員情報や取引データなどの業務データは、個人を特定できる情報を消し、件数や粒度を絞った場合に限って入力します。ソースコードや設計書は、承認済みのツールであれば入力できるとするのが一般的です。",{"q":34,"a":35},"設定ファイルでAIツールの読み取りを禁止すれば安全ですか？","設定は有効ですが、万能ではありません。たとえば Claude Code の読み取り禁止の設定は、ファイルを直接開く操作は止めますが、ファイル名を指定しない検索や、スクリプト経由の読み取りは止められません。設定と、人の行動ルールを組み合わせて運用します。",{"type":37,"children":38,"toc":1181},"root",[39,47,60,79,153,160,165,189,273,278,283,288,293,309,424,447,454,473,485,503,509,514,520,532,547,632,637,649,667,672,678,699,711,732,744,772,785,790,795,829,834,902,908,913,946,958,963,968,1049,1054,1076,1082,1087,1092,1121,1126],{"type":40,"tag":41,"props":42,"children":43},"element","p",{},[44],{"type":45,"value":46},"text","「外注先の開発会社が、うちのソースコードを AI に読ませているらしい。大丈夫なのか」——システム開発を外部に任せている会社から、こうした相談が増えています。",{"type":40,"tag":41,"props":48,"children":49},{},[50,52,58],{"type":45,"value":51},"実際、今の開発現場では、Claude Code、Cursor、GitHub Copilot、ChatGPT（Codex）などの AI ツールを使うのが当たり前になりつつあります。特に最近のツールは、エンジニアが貼り付けた文章に答えるだけでなく、",{"type":40,"tag":53,"props":54,"children":55},"strong",{},[56],{"type":45,"value":57},"自分でリポジトリの中のファイルを読み、コードを書き換え、コマンドを実行する",{"type":45,"value":59},"ところまで進んでいます。発注する側から見ると、「自社のコードや設定ファイルが、どこまで AI に渡っているのか」が見えにくくなっています。",{"type":40,"tag":41,"props":61,"children":62},{},[63,70,72,77],{"type":40,"tag":64,"props":65,"children":67},"a",{"href":66},"\u002Farticles\u002Fseisei-ai-shanai-rule-sample\u002F",[68],{"type":45,"value":69},"前編",{"type":45,"value":71},"では、全社員が業務で生成AIを使うときの社内ルールを扱いました。本記事（後編）では、",{"type":40,"tag":53,"props":73,"children":74},{},[75],{"type":45,"value":76},"システム開発を外注するときに、開発会社にどんな AI 利用ルールを約束してもらえばよいか",{"type":45,"value":78},"を、発注する側の視点で整理します。",{"type":40,"tag":80,"props":81,"children":82},"blockquote",{},[83,91],{"type":40,"tag":41,"props":84,"children":85},{},[86],{"type":40,"tag":53,"props":87,"children":88},{},[89],{"type":45,"value":90},"この記事の要点",{"type":40,"tag":92,"props":93,"children":94},"ul",{},[95,108,143,148],{"type":40,"tag":96,"props":97,"children":98},"li",{},[99,101,106],{"type":45,"value":100},"開発会社の AI ツール利用は、禁止するのではなく",{"type":40,"tag":53,"props":102,"children":103},{},[104],{"type":45,"value":105},"条件を決めて約束してもらう",{"type":45,"value":107},"のが現実的です。禁止すると生産性が落ちるか、ルールが守られなくなります",{"type":40,"tag":96,"props":109,"children":110},{},[111,113,118,120,125,126,131,132,137,138],{"type":45,"value":112},"約束してもらうのは5つです。",{"type":40,"tag":53,"props":114,"children":115},{},[116],{"type":45,"value":117},"外部連携アプリの事前合意",{"type":45,"value":119},"、",{"type":40,"tag":53,"props":121,"children":122},{},[123],{"type":45,"value":124},"AIツール利用の事前合意",{"type":45,"value":119},{"type":40,"tag":53,"props":127,"children":128},{},[129],{"type":45,"value":130},"秘密情報をプロンプトやログに載せない",{"type":45,"value":119},{"type":40,"tag":53,"props":133,"children":134},{},[135],{"type":45,"value":136},"AIの成果物は人がレビューしてからマージ",{"type":45,"value":119},{"type":40,"tag":53,"props":139,"children":140},{},[141],{"type":45,"value":142},"学習に使われない設定",{"type":40,"tag":96,"props":144,"children":145},{},[146],{"type":45,"value":147},"秘密情報は「ファイルの種類」ではなく「書かれている値」で3つに分け、設定ファイルで読ませない仕組みと人の行動ルールを組み合わせます。設定には限界があることも前提にします",{"type":40,"tag":96,"props":149,"children":150},{},[151],{"type":45,"value":152},"当社の現場では、そもそも社外のクラウドに出せない情報を扱う会社もありました。発注の最初に「どの情報を、どこで動く AI になら渡せるか」を決めておくと、見積もりと進め方がぶれません",{"type":40,"tag":154,"props":155,"children":157},"h2",{"id":156},"開発で使われるaiツールはチャット型とエージェント型に分かれる",[158],{"type":45,"value":159},"開発で使われるAIツールは「チャット型」と「エージェント型」に分かれる",{"type":40,"tag":41,"props":161,"children":162},{},[163],{"type":45,"value":164},"開発で使われる AI ツールは、発注する側から見たリスクの違いで、大きく2つに分けられます。",{"type":40,"tag":166,"props":167,"children":168},"picture",{},[169,171,179,180],{"type":45,"value":170},"\n  ",{"type":40,"tag":172,"props":173,"children":178},"source",{"media":174,"srcSet":175,"width":176,"height":177},"(max-width: 768px)","\u002Fimg\u002Fcontents\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule\u002Fchat-agent-sp.svg",420,560,[],{"type":45,"value":170},{"type":40,"tag":181,"props":182,"children":188},"img",{"src":183,"alt":184,"width":185,"height":186,"loading":187},"\u002Fimg\u002Fcontents\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule\u002Fchat-agent.svg","開発で使われるAIツールの2つの型：チャット型は人が貼り付けた内容だけをAIが見る。エージェント型はAIが自分でリポジトリのファイルを読み、コマンドを実行するため、設定ファイルでの制限が必要",800,330,"lazy",[],{"type":40,"tag":190,"props":191,"children":192},"table",{},[193,222],{"type":40,"tag":194,"props":195,"children":196},"thead",{},[197],{"type":40,"tag":198,"props":199,"children":200},"tr",{},[201,207,212,217],{"type":40,"tag":202,"props":203,"children":204},"th",{},[205],{"type":45,"value":206},"型",{"type":40,"tag":202,"props":208,"children":209},{},[210],{"type":45,"value":211},"主なツール",{"type":40,"tag":202,"props":213,"children":214},{},[215],{"type":45,"value":216},"AI が見るもの",{"type":40,"tag":202,"props":218,"children":219},{},[220],{"type":45,"value":221},"発注側から見たリスク",{"type":40,"tag":223,"props":224,"children":225},"tbody",{},[226,250],{"type":40,"tag":198,"props":227,"children":228},{},[229,235,240,245],{"type":40,"tag":230,"props":231,"children":232},"td",{},[233],{"type":45,"value":234},"チャット型",{"type":40,"tag":230,"props":236,"children":237},{},[238],{"type":45,"value":239},"ChatGPT・Claude・Gemini の Web やアプリ、Microsoft 365 Copilot",{"type":40,"tag":230,"props":241,"children":242},{},[243],{"type":45,"value":244},"人が貼り付けた内容だけ",{"type":40,"tag":230,"props":246,"children":247},{},[248],{"type":45,"value":249},"人がうっかり秘密情報を貼り付けること",{"type":40,"tag":198,"props":251,"children":252},{},[253,258,263,268],{"type":40,"tag":230,"props":254,"children":255},{},[256],{"type":45,"value":257},"エージェント型",{"type":40,"tag":230,"props":259,"children":260},{},[261],{"type":45,"value":262},"Claude Code、Cursor、ChatGPT の Codex、GitHub Copilot のエージェント機能",{"type":40,"tag":230,"props":264,"children":265},{},[266],{"type":45,"value":267},"AI が自分で開いたリポジトリ内のファイル、実行したコマンドの結果",{"type":40,"tag":230,"props":269,"children":270},{},[271],{"type":45,"value":272},"人が意識しないうちに、設定ファイルや認証情報まで AI が読むこと",{"type":40,"tag":41,"props":274,"children":275},{},[276],{"type":45,"value":277},"注意したいのは、エージェント型です。たとえば「ログインできない原因を調べて」と頼むと、AI は関係しそうなファイルを次々に開いていきます。その中に、本番環境のパスワードや API キーを書いた設定ファイルが含まれていれば、その値も AI に渡ります。エンジニア本人に悪意がなくても起こりうる点が、チャット型との大きな違いです。",{"type":40,"tag":41,"props":279,"children":280},{},[281],{"type":45,"value":282},"なお、チャット型でもデスクトップアプリでローカルのファイルやアプリと連携する機能（MCP など）を有効にしている場合は、エージェント型と同じ扱いにします。",{"type":40,"tag":154,"props":284,"children":286},{"id":285},"開発会社に約束してもらう5つの必須事項",[287],{"type":45,"value":285},{"type":40,"tag":41,"props":289,"children":290},{},[291],{"type":45,"value":292},"ルールの中心は、次の5つです。いずれも開発会社の生産性を大きく下げずに守れるもので、契約時の合意事項として明文化しておくことをおすすめします。",{"type":40,"tag":166,"props":294,"children":295},{},[296,297,302,303],{"type":45,"value":170},{"type":40,"tag":172,"props":298,"children":301},{"media":174,"srcSet":299,"width":176,"height":300},"\u002Fimg\u002Fcontents\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule\u002Fhissu-5-sp.svg",600,[],{"type":45,"value":170},{"type":40,"tag":181,"props":304,"children":308},{"src":305,"alt":306,"width":185,"height":307,"loading":187},"\u002Fimg\u002Fcontents\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule\u002Fhissu-5.svg","開発会社に約束してもらう5つの必須事項：外部連携アプリの事前合意、AIツール利用の事前合意、秘密情報をプロンプトやログに載せない、AIの成果物は人がレビューしてからマージ、学習に使われない設定",380,[],{"type":40,"tag":190,"props":310,"children":311},{},[312,333],{"type":40,"tag":194,"props":313,"children":314},{},[315],{"type":40,"tag":198,"props":316,"children":317},{},[318,323,328],{"type":40,"tag":202,"props":319,"children":320},{},[321],{"type":45,"value":322},"#",{"type":40,"tag":202,"props":324,"children":325},{},[326],{"type":45,"value":327},"必須事項",{"type":40,"tag":202,"props":329,"children":330},{},[331],{"type":45,"value":332},"内容",{"type":40,"tag":223,"props":334,"children":335},{},[336,353,370,388,406],{"type":40,"tag":198,"props":337,"children":338},{},[339,344,348],{"type":40,"tag":230,"props":340,"children":341},{},[342],{"type":45,"value":343},"1",{"type":40,"tag":230,"props":345,"children":346},{},[347],{"type":45,"value":117},{"type":40,"tag":230,"props":349,"children":350},{},[351],{"type":45,"value":352},"自社の GitHub などのリポジトリに、外部連携アプリ（GitHub App、AI のレビューボットなど）を事前の合意なしに入れない",{"type":40,"tag":198,"props":354,"children":355},{},[356,361,365],{"type":40,"tag":230,"props":357,"children":358},{},[359],{"type":45,"value":360},"2",{"type":40,"tag":230,"props":362,"children":363},{},[364],{"type":45,"value":124},{"type":40,"tag":230,"props":366,"children":367},{},[368],{"type":45,"value":369},"自社のコードや、自社が渡した資料を扱う AI ツールは、承認済みのものに限る。個人のアカウントで動くツールも対象にする",{"type":40,"tag":198,"props":371,"children":372},{},[373,378,383],{"type":40,"tag":230,"props":374,"children":375},{},[376],{"type":45,"value":377},"3",{"type":40,"tag":230,"props":379,"children":380},{},[381],{"type":45,"value":382},"秘密情報の保護",{"type":40,"tag":230,"props":384,"children":385},{},[386],{"type":45,"value":387},"秘密情報を、プロンプト、チャット、ログに載せない",{"type":40,"tag":198,"props":389,"children":390},{},[391,396,401],{"type":40,"tag":230,"props":392,"children":393},{},[394],{"type":45,"value":395},"4",{"type":40,"tag":230,"props":397,"children":398},{},[399],{"type":45,"value":400},"人によるレビュー",{"type":40,"tag":230,"props":402,"children":403},{},[404],{"type":45,"value":405},"AI が作成・変更した成果物は、人がレビューしてからマージする",{"type":40,"tag":198,"props":407,"children":408},{},[409,414,419],{"type":40,"tag":230,"props":410,"children":411},{},[412],{"type":45,"value":413},"5",{"type":40,"tag":230,"props":415,"children":416},{},[417],{"type":45,"value":418},"学習利用のオフ",{"type":40,"tag":230,"props":420,"children":421},{},[422],{"type":45,"value":423},"入力した内容が AI の学習に使われない設定（オプトアウト）をしたうえで使う",{"type":40,"tag":80,"props":425,"children":426},{},[427,435],{"type":40,"tag":41,"props":428,"children":429},{},[430],{"type":40,"tag":53,"props":431,"children":432},{},[433],{"type":45,"value":434},"K.S.Rogers の現場から",{"type":40,"tag":41,"props":436,"children":437},{},[438,440,445],{"type":45,"value":439},"当社が開発をお受けする場面では、5の「学習に使われない設定」だけでは足りない会社もありました。製造業の技術資料や、医療機関の患者情報のように、社内の決まりで",{"type":40,"tag":53,"props":441,"children":442},{},[443],{"type":45,"value":444},"そもそも社外のクラウドに出せない",{"type":45,"value":446},"情報を扱う場合です。こうした会社では、AI を社内の環境やオンプレミスで動かすことが前提になり、その費用が進め方を大きく左右しました。どの情報を AI に渡してよいか、どこで動く AI になら渡せるかを発注の最初に合意しておくと、見積もりも進め方もぶれません。",{"type":40,"tag":448,"props":449,"children":451},"h3",{"id":450},"_1と2の違い-アプリとツールは分けて考える",[452],{"type":45,"value":453},"1と2の違い ― 「アプリ」と「ツール」は分けて考える",{"type":40,"tag":41,"props":455,"children":456},{},[457,459,464,466,471],{"type":45,"value":458},"1の外部連携アプリは、リポジトリそのものに権限を持って組み込まれるため、影響が大きく、",{"type":40,"tag":53,"props":460,"children":461},{},[462],{"type":45,"value":463},"発注側の承認",{"type":45,"value":465},"を必須にします。一方、2の AI ツールは、エンジニアの手元で使うものです。毎回発注側が承認すると開発が止まるため、",{"type":40,"tag":53,"props":467,"children":468},{},[469],{"type":45,"value":470},"承認済みのツールの一覧を先に合意しておき、その範囲なら開発会社の中の確認で使ってよい",{"type":45,"value":472},"、とするのが現実的です。",{"type":40,"tag":41,"props":474,"children":475},{},[476,478,483],{"type":45,"value":477},"承認済みのツールは、Anthropic（Claude・Claude Code）、OpenAI（ChatGPT・Codex）、Microsoft と GitHub（GitHub Copilot・Microsoft 365 Copilot）、Anysphere（Cursor）、Google（Gemini）のように、",{"type":40,"tag":53,"props":479,"children":480},{},[481],{"type":45,"value":482},"提供元の会社単位",{"type":45,"value":484},"でリストにしておくと、新しい製品が出るたびに見直す手間が減ります。そのうえで、次のような条件を付けます。",{"type":40,"tag":92,"props":486,"children":487},{},[488,493,498],{"type":40,"tag":96,"props":489,"children":490},{},[491],{"type":45,"value":492},"どのツールも、5の「学習に使われない設定」をしていることが前提",{"type":40,"tag":96,"props":494,"children":495},{},[496],{"type":45,"value":497},"GitHub Copilot は、法人向けのプランに限る（リポジトリ側から読み取りを制限する機能が、法人向けのプランにしかないため）",{"type":40,"tag":96,"props":499,"children":500},{},[501],{"type":45,"value":502},"リストにないツールは、個別に申請して承認を受けるまで使わない",{"type":40,"tag":448,"props":504,"children":506},{"id":505},"_4は新しい手順を作らない",[507],{"type":45,"value":508},"4は「新しい手順」を作らない",{"type":40,"tag":41,"props":510,"children":511},{},[512],{"type":45,"value":513},"AI が書いたコードのレビューは、既存のプルリクエスト（PR）のレビューに組み込みます。PR の説明に「AI利用あり」と書く、レビュー担当者が AI が書いた部分を見分けられないときは作成者に確認する、レビューなしのマージはしない、の3点で十分です。AI 専用の承認手順を新しく作ると、手間が増えて守られなくなります。",{"type":40,"tag":154,"props":515,"children":517},{"id":516},"秘密情報は書かれている値で3つに分ける",[518],{"type":45,"value":519},"秘密情報は「書かれている値」で3つに分ける",{"type":40,"tag":41,"props":521,"children":522},{},[523,525,530],{"type":45,"value":524},"3の「秘密情報をプロンプトやログに載せない」を守るには、何が秘密情報なのかを決めておく必要があります。ポイントは、",{"type":40,"tag":53,"props":526,"children":527},{},[528],{"type":45,"value":529},"ファイルの種類ではなく、そこに書かれている値で判断する",{"type":45,"value":531},"ことです。同じ設定ファイルでも、ダミーの値なら秘密情報ではなく、本番の値なら秘密情報です。",{"type":40,"tag":166,"props":533,"children":534},{},[535,536,540,541],{"type":45,"value":170},{"type":40,"tag":172,"props":537,"children":539},{"media":174,"srcSet":538,"width":176,"height":177},"\u002Fimg\u002Fcontents\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule\u002Fhimitsu-3kubun-sp.svg",[],{"type":45,"value":170},{"type":40,"tag":181,"props":542,"children":546},{"src":543,"alt":544,"width":185,"height":545,"loading":187},"\u002Fimg\u002Fcontents\u002Farticles\u002Fkaihatsu-gaichu-ai-riyou-rule\u002Fhimitsu-3kubun.svg","秘密情報の3区分：区分Ⅰ認証情報はAIに入力不可（一部を伏せても不可）、区分Ⅱ顧客の業務データは匿名化の基準を満たせば可、区分Ⅲコードと設計書は承認済みツールなら可",300,[],{"type":40,"tag":190,"props":548,"children":549},{},[550,570],{"type":40,"tag":194,"props":551,"children":552},{},[553],{"type":40,"tag":198,"props":554,"children":555},{},[556,561,565],{"type":40,"tag":202,"props":557,"children":558},{},[559],{"type":45,"value":560},"区分",{"type":40,"tag":202,"props":562,"children":563},{},[564],{"type":45,"value":332},{"type":40,"tag":202,"props":566,"children":567},{},[568],{"type":45,"value":569},"AI ツールへの入力",{"type":40,"tag":223,"props":571,"children":572},{},[573,596,614],{"type":40,"tag":198,"props":574,"children":575},{},[576,581,586],{"type":40,"tag":230,"props":577,"children":578},{},[579],{"type":45,"value":580},"Ⅰ 認証情報",{"type":40,"tag":230,"props":582,"children":583},{},[584],{"type":45,"value":585},"パスワード、API キー、トークン、SSH の秘密鍵、証明書、クラウドの資格情報、Webhook の URL、本番環境の接続情報",{"type":40,"tag":230,"props":587,"children":588},{},[589,594],{"type":40,"tag":53,"props":590,"children":591},{},[592],{"type":45,"value":593},"不可",{"type":45,"value":595},"。一部を伏せた形でも入力しない",{"type":40,"tag":198,"props":597,"children":598},{},[599,604,609],{"type":40,"tag":230,"props":600,"children":601},{},[602],{"type":45,"value":603},"Ⅱ 業務データ",{"type":40,"tag":230,"props":605,"children":606},{},[607],{"type":45,"value":608},"会員情報（氏名・住所・電話番号・メールアドレス）、取引データ、請求データ",{"type":40,"tag":230,"props":610,"children":611},{},[612],{"type":45,"value":613},"原則不可。下の匿名化の基準を満たしたものだけ可",{"type":40,"tag":198,"props":615,"children":616},{},[617,622,627],{"type":40,"tag":230,"props":618,"children":619},{},[620],{"type":45,"value":621},"Ⅲ コードと設計",{"type":40,"tag":230,"props":623,"children":624},{},[625],{"type":45,"value":626},"ソースコード、データベースの定義、設計書、仕様書",{"type":40,"tag":230,"props":628,"children":629},{},[630],{"type":45,"value":631},"可。ただし承認済みの AI ツールに限る",{"type":40,"tag":41,"props":633,"children":634},{},[635],{"type":45,"value":636},"区分Ⅰを「一部を伏せても不可」としているのは、伏せ方が人によってばらつき、伏せ忘れが起きやすいためです。認証情報は、そもそも AI に見せない前提で扱います。",{"type":40,"tag":41,"props":638,"children":639},{},[640,642,647],{"type":45,"value":641},"区分Ⅱの業務データは、不具合の調査などでどうしても AI に見せたい場面があります。その場合は、次の基準を",{"type":40,"tag":53,"props":643,"children":644},{},[645],{"type":45,"value":646},"すべて",{"type":45,"value":648},"満たしたものに限ります。",{"type":40,"tag":92,"props":650,"children":651},{},[652,657,662],{"type":40,"tag":96,"props":653,"children":654},{},[655],{"type":45,"value":656},"氏名・住所・電話番号・メールアドレス・会員IDなど、個人を直接特定できる情報を削除するか、ダミーの値に置き換えている",{"type":40,"tag":96,"props":658,"children":659},{},[660],{"type":45,"value":661},"件数を必要最小限に絞っている（調査なら数件〜数十件）",{"type":40,"tag":96,"props":663,"children":664},{},[665],{"type":45,"value":666},"金額や日時を、個人の特定につながらない粒度（日単位、千円単位など）に丸めている",{"type":40,"tag":41,"props":668,"children":669},{},[670],{"type":45,"value":671},"迷ったときは入力せず、開発会社の品質責任者に確認する、というルールもセットにします。",{"type":40,"tag":154,"props":673,"children":675},{"id":674},"仕組みで守る-設定ファイルで読ませない",[676],{"type":45,"value":677},"仕組みで守る ― 設定ファイルで「読ませない」",{"type":40,"tag":41,"props":679,"children":680},{},[681,683,688,690,697],{"type":45,"value":682},"人の注意だけに頼らないために、エージェント型のツールには",{"type":40,"tag":53,"props":684,"children":685},{},[686],{"type":45,"value":687},"リポジトリ側で読み取りを禁止する設定",{"type":45,"value":689},"を置きます。たとえば Claude Code では、リポジトリに置いた設定ファイル（",{"type":40,"tag":691,"props":692,"children":694},"code",{"className":693},[],[695],{"type":45,"value":696},".claude\u002Fsettings.json",{"type":45,"value":698},"）に読み取り禁止のルールを書いてコミットすると、そのリポジトリを扱う全員に同じ制限がかかります。Cursor、Gemini、Codex、GitHub Copilot（法人向けプラン）にも、それぞれ同じような仕組みがあります。",{"type":40,"tag":41,"props":700,"children":701},{},[702,704,709],{"type":45,"value":703},"この方法のよいところは、",{"type":40,"tag":53,"props":705,"children":706},{},[707],{"type":45,"value":708},"メンバー個人の設定に依存しない",{"type":45,"value":710},"ことです。新しく参加したエンジニアも、リポジトリを取得した時点で同じ制限の下で作業することになります。設定の追加や変更も、通常の PR レビューを通すことで記録が残ります。",{"type":40,"tag":41,"props":712,"children":713},{},[714,716,722,724,730],{"type":45,"value":715},"ただし、設定には限界があります。K.S.Rogers で Claude Code の読み取り禁止の設定を検証したところ、ファイルを直接開く操作や ",{"type":40,"tag":691,"props":717,"children":719},{"className":718},[],[720],{"type":45,"value":721},"cat",{"type":45,"value":723}," などのコマンドでの読み取りは止まる一方、ファイル名を指定しない検索（",{"type":40,"tag":691,"props":725,"children":727},{"className":726},[],[728],{"type":45,"value":729},"grep",{"type":45,"value":731}," で全体を検索するなど）や、AI が書いたスクリプト経由の読み取りは止まりませんでした。",{"type":40,"tag":41,"props":733,"children":734},{},[735,737,742],{"type":45,"value":736},"そのため、設定と合わせて、次のような",{"type":40,"tag":53,"props":738,"children":739},{},[740],{"type":45,"value":741},"人の行動ルール",{"type":45,"value":743},"も決めておきます。",{"type":40,"tag":92,"props":745,"children":746},{},[747,752,757,762,767],{"type":40,"tag":96,"props":748,"children":749},{},[750],{"type":45,"value":751},"認証情報を、AI ツールのプロンプトやチャットに貼り付けない",{"type":40,"tag":96,"props":753,"children":754},{},[755],{"type":45,"value":756},"業務データを、匿名化の基準を満たさずに入力しない",{"type":40,"tag":96,"props":758,"children":759},{},[760],{"type":45,"value":761},"本番環境の設定ファイルの中身を、AI に読み上げさせたり要約させたりしない",{"type":40,"tag":96,"props":763,"children":764},{},[765],{"type":45,"value":766},"AI とのやりとりを、外部のサービスで共有・公開しない",{"type":40,"tag":96,"props":768,"children":769},{},[770],{"type":45,"value":771},"誤って入力したときは、すぐに報告する",{"type":40,"tag":41,"props":773,"children":774},{},[775,777,783],{"type":45,"value":776},"検証の詳しい結果（6つの読み取り経路で何が止まり、何が通ったか）と、各ツールの設定方法は、",{"type":40,"tag":64,"props":778,"children":780},{"href":779},"\u002Farticles\u002Fclaude-code-deny-settei\u002F",[781],{"type":45,"value":782},"Claude Codeの秘密情報対策｜読み取り禁止（deny）設定で防げること・防げないこと",{"type":45,"value":784},"で解説しています。",{"type":40,"tag":154,"props":786,"children":788},{"id":787},"運用を重くしない3つの原則",[789],{"type":45,"value":787},{"type":40,"tag":41,"props":791,"children":792},{},[793],{"type":45,"value":794},"AI 利用のルールは、細かくするほど守られなくなります。AI ツールの仕様は数か月単位で変わるため、細則を増やすと改定も追いつきません。運用は次の3つに絞ります。",{"type":40,"tag":796,"props":797,"children":798},"ol",{},[799,809,819],{"type":40,"tag":96,"props":800,"children":801},{},[802,807],{"type":40,"tag":53,"props":803,"children":804},{},[805],{"type":45,"value":806},"申請で把握する",{"type":45,"value":808}," ―― どのメンバーがどのツールを使っているかを、課題管理ツールの申請で記録する。承認の記録は申請の課題そのものとし、別の台帳は作らない",{"type":40,"tag":96,"props":810,"children":811},{},[812,817],{"type":40,"tag":53,"props":813,"children":814},{},[815],{"type":45,"value":816},"設定ファイルで統制する",{"type":45,"value":818}," ―― 秘密情報を読ませない設定をリポジトリ側に置き、個人の設定に依存しない",{"type":40,"tag":96,"props":820,"children":821},{},[822,827],{"type":40,"tag":53,"props":823,"children":824},{},[825],{"type":45,"value":826},"既存のプロセスに乗せる",{"type":45,"value":828}," ―― AI の成果物のレビューは既存の PR レビューに組み込み、新しい承認手順を作らない",{"type":40,"tag":41,"props":830,"children":831},{},[832],{"type":45,"value":833},"申請の項目も、A4 で半分ほどに収まる量にします。",{"type":40,"tag":190,"props":835,"children":836},{},[837,858],{"type":40,"tag":194,"props":838,"children":839},{},[840],{"type":40,"tag":198,"props":841,"children":842},{},[843,848,853],{"type":40,"tag":202,"props":844,"children":845},{},[846],{"type":45,"value":847},"申請の種類",{"type":40,"tag":202,"props":849,"children":850},{},[851],{"type":45,"value":852},"主な項目",{"type":40,"tag":202,"props":854,"children":855},{},[856],{"type":45,"value":857},"承認する人",{"type":40,"tag":223,"props":859,"children":860},{},[861,884],{"type":40,"tag":198,"props":862,"children":863},{},[864,869,874],{"type":40,"tag":230,"props":865,"children":866},{},[867],{"type":45,"value":868},"外部連携アプリ",{"type":40,"tag":230,"props":870,"children":871},{},[872],{"type":45,"value":873},"アプリ名と提供元、利用目的、対象リポジトリ（原則は特定のリポジトリに限る）、要求される権限、提供元でのデータの扱い",{"type":40,"tag":230,"props":875,"children":876},{},[877,879],{"type":45,"value":878},"開発会社の確認のうえ、",{"type":40,"tag":53,"props":880,"children":881},{},[882],{"type":45,"value":883},"発注側が最終承認",{"type":40,"tag":198,"props":885,"children":886},{},[887,892,897],{"type":40,"tag":230,"props":888,"children":889},{},[890],{"type":45,"value":891},"AI ツールの利用",{"type":40,"tag":230,"props":893,"children":894},{},[895],{"type":45,"value":896},"ツール名、契約プラン、コードや資料を読み込ませるか、エージェント型として使うか、学習に使われない設定の確認日",{"type":40,"tag":230,"props":898,"children":899},{},[900],{"type":45,"value":901},"開発会社の中の確認で可",{"type":40,"tag":154,"props":903,"children":905},{"id":904},"棚卸しメンバーの入れ替わり事故のとき",[906],{"type":45,"value":907},"棚卸し・メンバーの入れ替わり・事故のとき",{"type":40,"tag":41,"props":909,"children":910},{},[911],{"type":45,"value":912},"ルールを作って終わりにしないために、次の3つの場面の対応も決めておきます。",{"type":40,"tag":92,"props":914,"children":915},{},[916,926,936],{"type":40,"tag":96,"props":917,"children":918},{},[919,924],{"type":40,"tag":53,"props":920,"children":921},{},[922],{"type":45,"value":923},"半年に1回の棚卸し",{"type":45,"value":925}," ―― リポジトリに入っている外部連携アプリ、読み取り禁止の対象ファイル、承認済みツールの一覧、ツールのバージョンを確認する。発注側が求めたときは、結果を共有してもらう",{"type":40,"tag":96,"props":927,"children":928},{},[929,934],{"type":40,"tag":53,"props":930,"children":931},{},[932],{"type":45,"value":933},"メンバーの参画・離脱",{"type":45,"value":935}," ―― 参画時にルールを案内し、学習に使われない設定を確認する。離脱時には、リポジトリの権限と連携アプリの権限を外す",{"type":40,"tag":96,"props":937,"children":938},{},[939,944],{"type":40,"tag":53,"props":940,"children":941},{},[942],{"type":45,"value":943},"事故のとき",{"type":45,"value":945}," ―― 秘密情報を AI に入力した疑いがあるときは、発見した人がすぐに報告し、影響範囲を確認したうえで、必要なら認証情報を無効にして再発行する。発注側への報告の流れも決めておく",{"type":40,"tag":41,"props":947,"children":948},{},[949,951,956],{"type":45,"value":950},"事故の対応で特に大切なのは、",{"type":40,"tag":53,"props":952,"children":953},{},[954],{"type":45,"value":955},"自分から報告した人を不利に扱わない",{"type":45,"value":957},"と明記しておくことです。誤って入力したことを報告すると責められるルールでは、事故は隠れます。前編のサンプル条文でも、同じ考え方を入れています。",{"type":40,"tag":154,"props":959,"children":961},{"id":960},"発注側の確認チェックリスト",[962],{"type":45,"value":960},{"type":40,"tag":41,"props":964,"children":965},{},[966],{"type":45,"value":967},"開発会社と契約するとき、または今の契約を見直すときに、次の項目を確認します。",{"type":40,"tag":92,"props":969,"children":972},{"className":970},[971],"contains-task-list",[973,986,995,1004,1013,1022,1031,1040],{"type":40,"tag":96,"props":974,"children":977},{"className":975},[976],"task-list-item",[978,984],{"type":40,"tag":979,"props":980,"children":983},"input",{"disabled":981,"type":982},true,"checkbox",[],{"type":45,"value":985}," 開発会社が使っている AI ツールの一覧（提供元の単位）を共有してもらった",{"type":40,"tag":96,"props":987,"children":989},{"className":988},[976],[990,993],{"type":40,"tag":979,"props":991,"children":992},{"disabled":981,"type":982},[],{"type":45,"value":994}," どのツールも、入力内容が学習に使われない設定で使っていることを確認した",{"type":40,"tag":96,"props":996,"children":998},{"className":997},[976],[999,1002],{"type":40,"tag":979,"props":1000,"children":1001},{"disabled":981,"type":982},[],{"type":45,"value":1003}," 自社のリポジトリに外部連携アプリを入れるときは、自社の承認が必要だと合意した",{"type":40,"tag":96,"props":1005,"children":1007},{"className":1006},[976],[1008,1011],{"type":40,"tag":979,"props":1009,"children":1010},{"disabled":981,"type":982},[],{"type":45,"value":1012}," 認証情報を AI に入力しないこと、業務データは匿名化の基準を満たした場合に限ることを合意した",{"type":40,"tag":96,"props":1014,"children":1016},{"className":1015},[976],[1017,1020],{"type":40,"tag":979,"props":1018,"children":1019},{"disabled":981,"type":982},[],{"type":45,"value":1021}," エージェント型のツールについて、リポジトリ側で読み取りを禁止する設定を置いてもらった",{"type":40,"tag":96,"props":1023,"children":1025},{"className":1024},[976],[1026,1029],{"type":40,"tag":979,"props":1027,"children":1028},{"disabled":981,"type":982},[],{"type":45,"value":1030}," AI が作った成果物は、人がレビューしてからマージすることを確認した",{"type":40,"tag":96,"props":1032,"children":1034},{"className":1033},[976],[1035,1038],{"type":40,"tag":979,"props":1036,"children":1037},{"disabled":981,"type":982},[],{"type":45,"value":1039}," 半年に1回の棚卸しの結果を、求めれば共有してもらえることを確認した",{"type":40,"tag":96,"props":1041,"children":1043},{"className":1042},[976],[1044,1047],{"type":40,"tag":979,"props":1045,"children":1046},{"disabled":981,"type":982},[],{"type":45,"value":1048}," 事故が起きたときの報告の流れと、連絡先を決めた",{"type":40,"tag":41,"props":1050,"children":1051},{},[1052],{"type":45,"value":1053},"発注する側に技術の詳しい知識がなくても、この一覧を渡して「どう対応しているか」を聞くだけで、開発会社の管理の水準はかなり見えてきます。",{"type":40,"tag":80,"props":1055,"children":1056},{},[1057,1064],{"type":40,"tag":41,"props":1058,"children":1059},{},[1060],{"type":40,"tag":53,"props":1061,"children":1062},{},[1063],{"type":45,"value":434},{"type":40,"tag":41,"props":1065,"children":1066},{},[1067,1069,1074],{"type":45,"value":1068},"AI を使った開発を外部に任せるとき、当社の支援先で成果が続いているのは、",{"type":40,"tag":53,"props":1070,"children":1071},{},[1072],{"type":45,"value":1073},"丸投げにせず、計画・要件定義・開発を一緒に進めてノウハウを社内に残す",{"type":45,"value":1075},"会社です。作ったあとの運用が本番で、特定の外注先に頼り切りになると、担当者が変わったときに続きません。お客様自身が AI ツールで試作を作れる場合には、当社はゼロから作り直さず、その試作の精度を上げる役割に回ったこともあります。AI の利用ルールも同じで、発注側が中身を分かったうえで合意しておくことが、長く続けるための前提になります。",{"type":40,"tag":154,"props":1077,"children":1079},{"id":1078},"ksrogers-の考え方と支援",[1080],{"type":45,"value":1081},"K.S.Rogers の考え方と支援",{"type":40,"tag":41,"props":1083,"children":1084},{},[1085],{"type":45,"value":1086},"K.S.Rogers は、スタートアップスタジオ事業でお客様のプロダクト開発を担う立場でもあります。自社の開発でも、本記事と同じ考え方で AI ツールの利用ルールを定め、承認済みツールの管理、リポジトリ側の読み取り禁止の設定、PR レビューへの組み込みを運用しています。",{"type":40,"tag":41,"props":1088,"children":1089},{},[1090],{"type":45,"value":1091},"AI ツールは、正しく使えば開発の速さと品質を大きく引き上げます。止めるのではなく、安全に使える条件を先に決めて、発注する側と開発する側が同じルールの上で進める——それが、AI 時代の開発の外注に必要な前提だと考えています。",{"type":40,"tag":41,"props":1093,"children":1094},{},[1095,1097,1103,1105,1111,1113,1119],{"type":45,"value":1096},"「外注先の AI 利用について、何を確認すればよいか分からない」「開発を任せたいが、AI の扱いを含めて相談したい」という段階から、",{"type":40,"tag":64,"props":1098,"children":1100},{"href":1099},"\u002Frd\u002F",[1101],{"type":45,"value":1102},"要件定義支援",{"type":45,"value":1104},"や",{"type":40,"tag":64,"props":1106,"children":1108},{"href":1107},"\u002Fbusiness\u002Fss\u002F",[1109],{"type":45,"value":1110},"スタートアップスタジオ事業",{"type":45,"value":1112},"でご相談いただけます。ご相談は",{"type":40,"tag":64,"props":1114,"children":1116},{"href":1115},"\u002Fcontact\u002F",[1117],{"type":45,"value":1118},"お問い合わせ",{"type":45,"value":1120},"からどうぞ。",{"type":40,"tag":154,"props":1122,"children":1124},{"id":1123},"まとめ",[1125],{"type":45,"value":1123},{"type":40,"tag":92,"props":1127,"children":1128},{},[1129,1140,1152,1164,1176],{"type":40,"tag":96,"props":1130,"children":1131},{},[1132,1134,1138],{"type":45,"value":1133},"開発会社の AI ツール利用は、禁止ではなく",{"type":40,"tag":53,"props":1135,"children":1136},{},[1137],{"type":45,"value":105},{"type":45,"value":1139},"のが現実的です",{"type":40,"tag":96,"props":1141,"children":1142},{},[1143,1145,1150],{"type":45,"value":1144},"約束してもらうのは、外部連携アプリの事前合意、AIツール利用の事前合意、秘密情報をプロンプトやログに載せない、AIの成果物は人がレビューしてからマージ、学習に使われない設定、の",{"type":40,"tag":53,"props":1146,"children":1147},{},[1148],{"type":45,"value":1149},"5つ",{"type":45,"value":1151},"です",{"type":40,"tag":96,"props":1153,"children":1154},{},[1155,1157,1162],{"type":45,"value":1156},"秘密情報は",{"type":40,"tag":53,"props":1158,"children":1159},{},[1160],{"type":45,"value":1161},"書かれている値",{"type":45,"value":1163},"で、認証情報・業務データ・コードと設計の3つに分けます。認証情報は一部を伏せても入力しません",{"type":40,"tag":96,"props":1165,"children":1166},{},[1167,1169,1174],{"type":45,"value":1168},"エージェント型のツールには",{"type":40,"tag":53,"props":1170,"children":1171},{},[1172],{"type":45,"value":1173},"リポジトリ側の読み取り禁止の設定",{"type":45,"value":1175},"を置き、設定の限界を人の行動ルールで補います",{"type":40,"tag":96,"props":1177,"children":1178},{},[1179],{"type":45,"value":1180},"運用は、申請で把握する、設定ファイルで統制する、既存のプロセスに乗せる、の3つに絞ります",{"title":7,"searchDepth":1182,"depth":1182,"links":1183},2,[1184,1185,1190,1191,1192,1193,1194,1195,1196],{"id":156,"depth":1182,"text":159},{"id":285,"depth":1182,"text":285,"children":1186},[1187,1189],{"id":450,"depth":1188,"text":453},3,{"id":505,"depth":1188,"text":508},{"id":516,"depth":1182,"text":519},{"id":674,"depth":1182,"text":677},{"id":787,"depth":1182,"text":787},{"id":904,"depth":1182,"text":907},{"id":960,"depth":1182,"text":960},{"id":1078,"depth":1182,"text":1081},{"id":1123,"depth":1182,"text":1123},"markdown","content:articles:kaihatsu-gaichu-ai-riyou-rule.md","content","articles\u002Fkaihatsu-gaichu-ai-riyou-rule.md","articles\u002Fkaihatsu-gaichu-ai-riyou-rule","md",[1204,1209,1214,1218,1223,1228,1232,1237,1242,1247],{"_path":1205,"title":1206,"seriesNo":1207,"seriesLabel":1208},"\u002Farticles\u002Fm365-copilot-donyu-roadmap","Microsoft 365 Copilot 導入ロードマップ｜非IT企業がライセンス配布前に決めること",1,"第1回",{"_path":1210,"title":1211,"seriesNo":1212,"seriesLabel":1213},"\u002Farticles\u002Fcopilot-shanai-kitei-edp","Copilotのエンタープライズデータ保護（EDP）とは｜「外部AI禁止」の社内規程でも使えるかの判断手順",1.5,"特別編",{"_path":1215,"title":1216,"seriesNo":1182,"seriesLabel":1217},"\u002Farticles\u002Fcopilot-data-okiba-box-sharepoint","Copilotは社内データを学習する？｜参照できるデータの条件とSharePoint・OneDrive・Boxの使い分け","第2回（前編）",{"_path":1219,"title":1220,"seriesNo":1221,"seriesLabel":1222},"\u002Farticles\u002Fcopilot-mail-chat-ikou-checklist","Exchange Online移行の注意点とLINE WORKSからTeamsへの判断｜Microsoft 365 Copilot導入前チェックリスト",2.5,"第2回（後編）",{"_path":1224,"title":1225,"seriesNo":1226,"seriesLabel":1227},"\u002Farticles\u002Fm365-copilot-iranai-google-hikaku","Microsoft 365 Copilotはいらない？無料版との違い・料金と「Googleより高い」への答え方",2.8,"番外編",{"_path":1229,"title":1230,"seriesNo":1188,"seriesLabel":1231},"\u002Farticles\u002Fcopilot-joho-rouei-sharepoint-kengen","Microsoft 365 Copilotの情報漏洩対策｜SharePoint・OneDrive・Teamsの権限を棚卸しして是正する手順","第3回",{"_path":1233,"title":1234,"seriesNo":1235,"seriesLabel":1236},"\u002Farticles\u002Fcopilot-security-settei-chusho","Microsoft 365 Copilotのセキュリティ設定｜中小企業に秘密度ラベルとDLPは必要か",4,"第4回（前編）",{"_path":1238,"title":1239,"seriesNo":1240,"seriesLabel":1241},"\u002Farticles\u002Fcopilot-sensitivity-label-dlp","Microsoft 365 Copilotの秘密度ラベルとDLP｜「警告」から始める段階設計とライセンス要件",4.5,"第4回（後編）",{"_path":1243,"title":1244,"seriesNo":1245,"seriesLabel":1246},"\u002Farticles\u002Fseisei-ai-shanai-rule-sample","生成AIの社内ルールの作り方【サンプル条文付き】｜Microsoft 365 Copilot時代の利用ガイドライン",5,"第5回（前編）",{"_path":4,"title":8,"seriesNo":13,"seriesLabel":14},1792102873257]