[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"quiz:kjh-mock-kadai-2-v5":3,"quiz-article-index":1173},{"quizId":4,"title":5,"titleEn":6,"topicPath":7,"questions":8},"kjh-mock-kadai-2-v5","課題Ⅱ 模擬試験（第5回）","Subject II Mock Exam #5","software\u002Fkojin-joho-hogo\u002Fkadai-2",[9,37,61,84,107,131,154,177,201,223,247,271,294,318,341,364,388,412,436,459,483,507,530,553,577,599,622,645,667,689,712,736,760,783,807,830,853,877,900,922,944,967,984,1008,1032,1055,1080,1103,1127,1148],{"id":10,"articleId":11,"question":12,"options":15,"correctLabel":17,"explanation":32,"tags":35},"kjh-mock-k2v5-q01","kjh-k2-h01-security-kiso",{"en":13,"jp":14},"Which are correctly described as additional properties beyond the CIA triad in information security?","[情報]{じょうほう:information}セキュリティのCIAに[追加]{ついか:additional}される[特性]{とくせい:properties}として[正]{ただ:correct}しいものはどれか。",[16,20,24,28],{"label":17,"jp":18,"en":19},"ア","[真正性]{しんせいせい:authenticity}・[責任]{せきにん:accountability}[追跡性]{ついせきせい:traceability}・[否認]{ひにん:non-repudiation}[防止]{ぼうし:prevention}・[信頼性]{しんらいせい:reliability}","Authenticity, Accountability, Non-repudiation, Reliability",{"label":21,"jp":22,"en":23},"イ","[速度]{そくど:speed}・[効率性]{こうりつせい:efficiency}・[経済性]{けいざいせい:economy}","Speed, Efficiency, Economy",{"label":25,"jp":26,"en":27},"ウ","[機密性]{きみつせい:confidentiality}・[完全性]{かんぜんせい:integrity}・[可用性]{かようせい:availability}","Confidentiality, Integrity, Availability",{"label":29,"jp":30,"en":31},"エ","ハードウェア・ソフトウェア・ネットワーク","Hardware, Software, Network",{"en":33,"jp":34},"Additional properties beyond the CIA triad include authenticity, accountability, non-repudiation, and reliability. Option C is the CIA triad itself.","CIAの3[要素]{ようそ:elements}（[機密性]{きみつせい:confidentiality}・[完全性]{かんぜんせい:integrity}・[可用性]{かようせい:availability}）に[追加]{ついか:additional}される[特性]{とくせい:properties}として、[真正性]{しんせいせい:authenticity}、[責任]{せきにん:accountability}[追跡性]{ついせきせい:traceability}、[否認]{ひにん:non-repudiation}[防止]{ぼうし:prevention}、[信頼性]{しんらいせい:reliability}がある。ウはCIAそのもの。",[36],"CIA",{"id":38,"articleId":11,"question":39,"options":42,"correctLabel":21,"explanation":55,"tags":58},"kjh-mock-k2v5-q02",{"en":40,"jp":41},"What is a collection of bot-infected computers called?","ボットに[感染]{かんせん:infected}したコンピュータの[集合]{しゅうごう:collection}を[何]{なん:what}と[呼]{よ:call}ぶか。",[43,46,49,52],{"label":17,"jp":44,"en":45},"ファイアウォール","Firewall",{"label":21,"jp":47,"en":48},"ボットネット","Botnet",{"label":25,"jp":50,"en":51},"ハニーポット","Honeypot",{"label":29,"jp":53,"en":54},"サンドボックス","Sandbox",{"en":56,"jp":57},"A botnet is a collection of computers infected with bots (remote control malware). Attackers send simultaneous commands via C&C servers for DDoS attacks or spam. A honeypot is a decoy system to attract attacks.","ボットネットは、ボット（[遠隔]{えんかく:remote}[操作]{そうさ:control}マルウェア）に[感染]{かんせん:infected}したコンピュータの[集合]{しゅうごう:collection}。[攻撃者]{こうげきしゃ:attacker}はC&Cサーバを[通]{つう:through}じて[一斉]{いっせい:simultaneously}に[命令]{めいれい:commands}を[送]{おく:send}り、DDoS[攻撃]{こうげき:attacks}やスパムメール[送信]{そうしん:sending}に[利用]{りよう:use}する。ハニーポットは[攻撃]{こうげき:attacks}を[誘引]{ゆういん:attract}する[囮]{おとり:decoy}システム。",[59,60],"malware","botnet",{"id":62,"articleId":11,"question":63,"options":66,"correctLabel":21,"explanation":79,"tags":82},"kjh-mock-k2v5-q03",{"en":64,"jp":65},"What is a phishing attack using SMS called?","SMSを[使]{つか:use}ったフィッシング[攻撃]{こうげき:attack}を[何]{なん:what}と[呼]{よ:call}ぶか。",[67,70,73,76],{"label":17,"jp":68,"en":69},"ビッシング","Vishing",{"label":21,"jp":71,"en":72},"スミッシング","Smishing",{"label":25,"jp":74,"en":75},"ファーミング","Pharming",{"label":29,"jp":77,"en":78},"スキミング","Skimming",{"en":80,"jp":81},"Smishing is phishing via SMS. Vishing uses voice calls. Pharming alters DNS to redirect to fake sites. Skimming is unauthorized card information reading.","スミッシング（SMiShing）はSMSを[使]{つか:use}ったフィッシング[攻撃]{こうげき:attack}。ビッシング（Vishing）は[音声]{おんせい:voice}[通話]{つうわ:call}を[使]{つか:use}ったフィッシング。ファーミングはDNSを[改]{かい:alter}ざんして[偽]{にせ:fake}サイトに[誘導]{ゆうどう:redirect}する[攻撃]{こうげき:attack}。スキミングはカード[情報]{じょうほう:information}の[不正]{ふせい:unauthorized}[読取]{よみと:reading}り。",[83],"phishing",{"id":85,"articleId":11,"question":86,"options":89,"correctLabel":21,"explanation":102,"tags":105},"kjh-mock-k2v5-q04",{"en":87,"jp":88},"Which type of XSS attack has the attack script stored on the server?","XSS[攻撃]{こうげき:attack}の[種類]{しゅるい:type}のうち、[攻撃]{こうげき:attack}スクリプトがサーバに[保存]{ほぞん:stored}されるものはどれか。",[90,93,96,99],{"label":17,"jp":91,"en":92},"[反射型]{はんしゃがた:reflected}XSS","Reflected XSS",{"label":21,"jp":94,"en":95},"[格納型]{かくのうがた:stored}XSS","Stored XSS",{"label":25,"jp":97,"en":98},"DOMベースXSS","DOM-based XSS",{"label":29,"jp":100,"en":101},"SQLインジェクション","SQL injection",{"en":103,"jp":104},"Stored XSS has attack scripts stored on the server (e.g., database), executed whenever other users browse that page. Reflected XSS reflects scripts from the request in the response.","[格納型]{かくのうがた:stored}XSSは、[攻撃]{こうげき:attack}スクリプトがサーバ（データベースなど）に[保存]{ほぞん:stored}され、[他]{た:other}の[利用者]{りようしゃ:users}がそのページを[閲覧]{えつらん:browse}する[度]{たび:time}にスクリプトが[実行]{じっこう:executed}される。[反射型]{はんしゃがた:reflected}はリクエストに[含]{ふく:included}まれたスクリプトがレスポンスに[反映]{はんえい:reflected}される。",[106],"XSS",{"id":108,"articleId":109,"question":110,"options":113,"correctLabel":17,"explanation":126,"tags":129},"kjh-mock-k2v5-q05","kjh-k2-h04-gijutsu-kiso",{"en":111,"jp":112},"Which correctly describes the mechanism of token verification as a CSRF countermeasure?","CSRF[対策]{たいさく:countermeasure}のトークン[検証]{けんしょう:verification}の[仕組]{しく:mechanism}みとして[正]{ただ:correct}しいものはどれか。",[114,117,120,123],{"label":17,"jp":115,"en":116},"フォームに[秘密]{ひみつ:secret}のトークンを[埋]{う:embed}め[込]{こ:insert}み、リクエスト[時]{じ:time}にサーバ[側]{がわ:side}で[照合]{しょうごう:verify}する","Embedding a secret token in the form and verifying it server-side upon request",{"label":21,"jp":118,"en":119},"[全]{すべ:all}てのリクエストを[暗号化]{あんごうか:encrypt}する","Encrypting all requests",{"label":25,"jp":121,"en":122},"IPアドレスで[利用者]{りようしゃ:user}を[判別]{はんべつ:identify}する","Identifying users by IP address",{"label":29,"jp":124,"en":125},"パスワードを[毎回]{まいかい:every time}[入力]{にゅうりょく:input}させる","Requiring password input every time",{"en":127,"jp":128},"A CSRF token is generated by the server, embedded in forms, and verified server-side upon request. Since attackers cannot know the token, they cannot send malicious requests.","CSRFトークンは、サーバが[生成]{せいせい:generate}した[推測]{すいそく:guess}[困難]{こんなん:difficult}なトークンをフォームに[埋]{う:embed}め[込]{こ:insert}み、リクエスト[時]{じ:time}にサーバ[側]{がわ:side}で[照合]{しょうごう:verify}する[仕組]{しく:mechanism}み。[攻撃者]{こうげきしゃ:attacker}はトークンを[知]{し:know}ることができないため[不正]{ふせい:malicious}リクエストを[送]{おく:send}れない。",[130],"CSRF",{"id":132,"articleId":11,"question":133,"options":136,"correctLabel":17,"explanation":149,"tags":152},"kjh-mock-k2v5-q06",{"en":134,"jp":135},"Which correctly describes a characteristic of a zero-day attack?","ゼロデイ[攻撃]{こうげき:attack}の[特徴]{とくちょう:characteristic}として[正]{ただ:correct}しいものはどれか。",[137,140,143,146],{"label":17,"jp":138,"en":139},"[脆弱性]{ぜいじゃくせい:vulnerability}の[修正]{しゅうせい:fix}パッチが[公開]{こうかい:released}される[前]{まえ:before}にその[脆弱性]{ぜいじゃくせい:vulnerability}を[悪用]{あくよう:exploit}する[攻撃]{こうげき:attack}","An attack exploiting a vulnerability before a fix patch is released",{"label":21,"jp":141,"en":142},"[毎日]{まいにち:daily}[午前]{ごぜん:morning}0[時]{じ:o'clock}に[行]{おこな:carried out}われる[攻撃]{こうげき:attack}","An attack carried out every day at midnight",{"label":25,"jp":144,"en":145},"0[回]{かい:times}の[試行]{しこう:attempt}でパスワードを[破]{やぶ:break}る[攻撃]{こうげき:attack}","An attack that breaks passwords with zero attempts",{"label":29,"jp":147,"en":148},"[既知]{きち:known}の[脆弱性]{ぜいじゃくせい:vulnerability}のみを[利用]{りよう:use}する[攻撃]{こうげき:attack}","An attack using only known vulnerabilities",{"en":150,"jp":151},"A zero-day attack exploits a vulnerability during the period between discovery and patch provision (the zero day). It is extremely dangerous because no countermeasures exist.","ゼロデイ[攻撃]{こうげき:attack}は、[脆弱性]{ぜいじゃくせい:vulnerability}が[発見]{はっけん:discovered}されてから[修正]{しゅうせい:fix}パッチが[提供]{ていきょう:provided}されるまでの[期間]{きかん:period}（ゼロデイ）にその[脆弱性]{ぜいじゃくせい:vulnerability}を[悪用]{あくよう:exploit}する[攻撃]{こうげき:attack}。[対策]{たいさく:countermeasures}が[存在]{そんざい:exist}しないため[非常]{ひじょう:extremely}に[危険]{きけん:dangerous}。",[153],"targeted-attack",{"id":155,"articleId":11,"question":156,"options":159,"correctLabel":17,"explanation":172,"tags":175},"kjh-mock-k2v5-q07",{"en":157,"jp":158},"What is an important effort from the perspective of supply chain risk management?","サプライチェーンリスク[管理]{かんり:management}の[観点]{かんてん:perspective}から[重要]{じゅうよう:important}な[取]{と:effort}り[組]{く:effort}みはどれか。",[160,163,166,169],{"label":17,"jp":161,"en":162},"[取引先]{とりひきさき:business partner}のセキュリティ[対策]{たいさく:measures}[状況]{じょうきょう:status}を[定期的]{ていきてき:periodically}に[確認]{かくにん:verify}する","Periodically verifying business partners' security measures status",{"label":21,"jp":164,"en":165},"[取引先]{とりひきさき:business partners}の[数]{かず:number}を[増]{ふ:increase}やす","Increasing the number of business partners",{"label":25,"jp":167,"en":168},"ソフトウェアの[更新]{こうしん:updates}を[行]{おこな:carry out}わない","Not carrying out software updates",{"label":29,"jp":170,"en":171},"[自社]{じしゃ:own company}のセキュリティ[対策]{たいさく:measures}のみに[注力]{ちゅうりょく:focus}する","Focusing only on one's own company's security measures",{"en":173,"jp":174},"In supply chain risk management, it is important to periodically verify and audit business partners' security status, not just one's own. Partner vulnerabilities can become attack routes to one's own company.","サプライチェーンリスク[管理]{かんり:management}では、[自社]{じしゃ:own company}だけでなく[取引先]{とりひきさき:business partners}のセキュリティ[対策]{たいさく:measures}[状況]{じょうきょう:status}を[定期的]{ていきてき:periodically}に[確認]{かくにん:verify}・[監査]{かんさ:audit}することが[重要]{じゅうよう:important}。[取引先]{とりひきさき:business partners}の[脆弱性]{ぜいじゃくせい:vulnerabilities}が[自社]{じしゃ:own company}への[攻撃]{こうげき:attacks}[経路]{けいろ:routes}になりうる。",[176],"supply-chain",{"id":178,"articleId":109,"question":179,"options":182,"correctLabel":21,"explanation":195,"tags":198},"kjh-mock-k2v5-q08",{"en":180,"jp":181},"Which correctly describes a password list attack?","パスワードリスト[攻撃]{こうげき:attack}の[説明]{せつめい:description}として[正]{ただ:correct}しいものはどれか。",[183,186,189,192],{"label":17,"jp":184,"en":185},"[全]{すべ:all}ての[文字]{もじ:character}[組]{く:combination}み[合]{あ:combination}わせを[試]{ため:try}す","Trying all character combinations",{"label":21,"jp":187,"en":188},"[他]{た:other}のサービスから[流出]{りゅうしゅつ:leaked}したID・パスワードのリストを[使]{つか:use}ってログインを[試]{こころ:attempt}みる","Attempting login using a list of IDs\u002Fpasswords leaked from other services",{"label":25,"jp":190,"en":191},"[辞書]{じしょ:dictionary}に[掲載]{けいさい:listed}されている[単語]{たんご:words}を[順番]{じゅんばん:sequentially}に[試]{ため:try}す","Trying dictionary words sequentially",{"label":29,"jp":193,"en":194},"ソーシャルエンジニアリングでパスワードを[聞]{き:ask}き[出]{だ:extract}す","Extracting passwords through social engineering",{"en":196,"jp":197},"Password list attacks use leaked authentication data from other services to target users who reuse passwords. A is brute force; C is a dictionary attack.","パスワードリスト[攻撃]{こうげき:attack}は、[他]{た:other}のサービスから[流出]{りゅうしゅつ:leaked}した[認証]{にんしょう:authentication}[情報]{じょうほう:information}のリストを[使]{つか:use}い、パスワードの[使]{つか:reuse}い[回]{まわ:reuse}しをしている[利用者]{りようしゃ:users}を[狙]{ねら:target}う[攻撃]{こうげき:attack}。アはブルートフォース、ウは[辞書]{じしょ:dictionary}[攻撃]{こうげき:attack}。",[199,200],"DDoS","social-engineering",{"id":202,"articleId":11,"question":203,"options":206,"correctLabel":25,"explanation":219,"tags":222},"kjh-mock-k2v5-q09",{"en":204,"jp":205},"Which is the most effective countermeasure against social engineering?","ソーシャルエンジニアリング[対策]{たいさく:countermeasures}として[最]{もっと:most}も[有効]{ゆうこう:effective}なものはどれか。",[207,210,213,216],{"label":17,"jp":208,"en":209},"ファイアウォールの[強化]{きょうか:strengthening}","Strengthening the firewall",{"label":21,"jp":211,"en":212},"[暗号化]{あんごうか:encryption}[技術]{ぎじゅつ:technology}の[導入]{どうにゅう:introduction}","Introducing encryption technology",{"label":25,"jp":214,"en":215},"[従業者]{じゅうぎょうしゃ:employees}へのセキュリティ[意識]{いしき:awareness}[教育]{きょういく:education}","Security awareness education for employees",{"label":29,"jp":217,"en":218},"サーバの[冗長化]{じょうちょうか:redundancy}","Server redundancy",{"en":220,"jp":221},"Since social engineering exploits human psychology, technical measures alone cannot prevent it. Periodic security awareness education for employees is most effective.","ソーシャルエンジニアリングは[人間]{にんげん:human}の[心理]{しんり:psychology}を[突]{つ:exploit}く[攻撃]{こうげき:attack}であるため、[技術的]{ぎじゅつてき:technical}な[対策]{たいさく:measures}だけでは[防]{ふせ:prevent}げない。[従業者]{じゅうぎょうしゃ:employees}への[定期的]{ていきてき:periodic}なセキュリティ[意識]{いしき:awareness}[教育]{きょういく:education}が[最]{もっと:most}も[有効]{ゆうこう:effective}。",[200],{"id":224,"articleId":225,"question":226,"options":229,"correctLabel":21,"explanation":242,"tags":245},"kjh-mock-k2v5-q10","kjh-k2-h01-guideline",{"en":227,"jp":228},"Which correctly describes penalties under the Unauthorized Computer Access Law?","[不正]{ふせい:unauthorized}アクセス[禁止法]{きんしほう:prohibition law}の[罰則]{ばっそく:penalties}として[正]{ただ:correct}しいものはどれか。",[230,233,236,239],{"label":17,"jp":231,"en":232},"[罰則]{ばっそく:penalties}はなく[行政]{ぎょうせい:administrative}[指導]{しどう:guidance}のみ","No penalties; only administrative guidance",{"label":21,"jp":234,"en":235},"[不正]{ふせい:unauthorized}アクセス[行為]{こうい:act}に[対]{たい:for}して[懲役]{ちょうえき:imprisonment}または[罰金]{ばっきん:fine}が[科]{か:imposed}される","Imprisonment or fine is imposed for unauthorized access acts",{"label":25,"jp":237,"en":238},"[民事]{みんじ:civil}[責任]{せきにん:liability}のみで[刑事]{けいじ:criminal}[罰]{ばつ:penalties}はない","Only civil liability; no criminal penalties",{"label":29,"jp":240,"en":241},"[企業]{きぎょう:companies}のみが[対象]{たいしょう:subject}で[個人]{こじん:individuals}は[対象外]{たいしょうがい:outside scope}","Only companies are subject; individuals are outside scope",{"en":243,"jp":244},"The law carries criminal penalties: up to 3 years imprisonment or up to 1 million yen fine for unauthorized access acts. Individuals are also subject.","[不正]{ふせい:unauthorized}アクセス[禁止法]{きんしほう:prohibition law}は[刑事]{けいじ:criminal}[罰]{ばつ:penalties}を[伴]{ともな:accompany}う[法律]{ほうりつ:law}であり、[不正]{ふせい:unauthorized}アクセス[行為]{こうい:acts}に[対]{たい:for}して3[年]{ねん:years}[以下]{いか:or less}の[懲役]{ちょうえき:imprisonment}または100[万]{まん:ten thousand}[円]{えん:yen}[以下]{いか:or less}の[罰金]{ばっきん:fine}が[科]{か:imposed}される。[個人]{こじん:individuals}も[対象]{たいしょう:subject}。",[246],"unauthorized-access-law",{"id":248,"articleId":249,"question":250,"options":253,"correctLabel":21,"explanation":266,"tags":269},"kjh-mock-k2v5-q11","kjh-k1-h01-hotaikei",{"en":251,"jp":252},"What would cause trade secrets to lose their \"non-public knowledge\" status?","[営業]{えいぎょう:trade}[秘密]{ひみつ:secret}の「[非]{ひ:non-}[公知性]{こうちせい:public knowledge}」を[失]{うしな:lose}う[原因]{げんいん:cause}となるものはどれか。",[254,257,260,263],{"label":17,"jp":255,"en":256},"[社内]{しゃない:internal}の[限]{かぎ:limited}られた[関係者]{かんけいしゃ:personnel}のみが[知]{し:know}っている","Only limited internal personnel know",{"label":21,"jp":258,"en":259},"[学術]{がくじゅつ:academic}[論文]{ろんぶん:paper}で[公表]{こうひょう:published}してしまう","Publishing in an academic paper",{"label":25,"jp":261,"en":262},"[金庫]{きんこ:safe}に[保管]{ほかん:stored}する","Storing in a safe",{"label":29,"jp":264,"en":265},"アクセス[制限]{せいげん:restrictions}をかける","Applying access restrictions",{"en":267,"jp":268},"\"Non-public knowledge\" means not publicly known. Publication in academic papers or newspaper coverage makes it public knowledge, no longer satisfying this requirement.","「[非]{ひ:non-}[公知性]{こうちせい:public knowledge}」は、[公然]{こうぜん:publicly}と[知]{し:known}られていない[状態]{じょうたい:state}を[意味]{いみ:mean}する。[学術]{がくじゅつ:academic}[論文]{ろんぶん:paper}での[公表]{こうひょう:publication}や[新聞]{しんぶん:newspaper}[報道]{ほうどう:coverage}により[公知]{こうち:public knowledge}となると、[非]{ひ:non-}[公知性]{こうちせい:public knowledge}の[要件]{ようけん:requirement}を[満]{み:satisfy}たさなくなる。",[270],"unfair-competition-law",{"id":272,"articleId":225,"question":273,"options":276,"correctLabel":17,"explanation":289,"tags":292},"kjh-mock-k2v5-q12",{"en":274,"jp":275},"What is the responsibility of \"business operators\" under the Basic Act on Cybersecurity?","サイバーセキュリティ[基本法]{きほんほう:basic act}における「[事業者]{じぎょうしゃ:business operators}」の[責務]{せきむ:responsibility}はどれか。",[277,280,283,286],{"label":17,"jp":278,"en":279},"[自主的]{じしゅてき:voluntarily}かつ[積極的]{せっきょくてき:proactively}にサイバーセキュリティの[確保]{かくほ:ensure}に[努]{つと:strive}めること","Voluntarily and proactively striving to ensure cybersecurity",{"label":21,"jp":281,"en":282},"[国]{くに:nation}がすべてのセキュリティ[対策]{たいさく:measures}を[実施]{じっし:implement}するので[事業者]{じぎょうしゃ:operators}は[何]{なに:anything}もしなくてよい","The nation implements all security measures so operators need do nothing",{"label":25,"jp":284,"en":285},"サイバーセキュリティ[対策]{たいさく:measures}は[任意]{にんい:optional}","Cybersecurity measures are optional",{"label":29,"jp":287,"en":288},"[従業員]{じゅうぎょういん:employees}10[名]{めい:persons}[以上]{いじょう:or more}の[企業]{きぎょう:companies}のみ[対象]{たいしょう:subject}","Only companies with 10+ employees are subject",{"en":290,"jp":291},"The Act imposes on business operators the responsibility to voluntarily and proactively strive to ensure cybersecurity. There are no size-based restrictions.","サイバーセキュリティ[基本法]{きほんほう:basic act}は、[事業者]{じぎょうしゃ:business operators}に[自主的]{じしゅてき:voluntarily}かつ[積極的]{せっきょくてき:proactively}にサイバーセキュリティの[確保]{かくほ:ensure}に[努]{つと:strive}める[責務]{せきむ:responsibility}を[課]{か:impose}している。[規模]{きぼ:size}による[制限]{せいげん:restrictions}はない。",[293],"cybersecurity-basic-act",{"id":295,"articleId":249,"question":296,"options":299,"correctLabel":17,"explanation":312,"tags":315},"kjh-mock-k2v5-q13",{"en":297,"jp":298},"Which correctly describes the difference in certification scope between P-Mark and ISMS?","P-MarkとISMSの[認証]{にんしょう:certification}[範囲]{はんい:scope}の[違]{ちが:difference}いとして[正]{ただ:correct}しいものはどれか。",[300,303,306,309],{"label":17,"jp":301,"en":302},"P-Markは[事業者]{じぎょうしゃ:operator}[全体]{ぜんたい:entire}、ISMSは[範囲]{はんい:scope}を[限定]{げんてい:limit}して[取得]{しゅとく:obtain}[可能]{かのう:possible}","P-Mark covers the entire operator; ISMS can be obtained for a limited scope",{"label":21,"jp":304,"en":305},"[両方]{りょうほう:both}とも[事業者]{じぎょうしゃ:operator}[全体]{ぜんたい:entire}が[対象]{たいしょう:scope}","Both cover the entire operator",{"label":25,"jp":307,"en":308},"ISMSは[事業者]{じぎょうしゃ:operator}[全体]{ぜんたい:entire}、P-Markは[部門]{ぶもん:department}[単位]{たんい:unit}","ISMS covers the entire operator; P-Mark is department-level",{"label":29,"jp":310,"en":311},"[両方]{りょうほう:both}とも[部門]{ぶもん:department}[単位]{たんい:unit}で[取得]{しゅとく:obtain}[可能]{かのう:possible}","Both can be obtained at the department level",{"en":313,"jp":314},"P-Mark must be obtained for the entire operator (legal entity). ISMS can be obtained for a limited scope (specific department or service) within the organization.","P-Markは[事業者]{じぎょうしゃ:operator}[全体]{ぜんたい:entire}（[法人]{ほうじん:legal entity}[単位]{たんい:unit}）での[取得]{しゅとく:acquisition}が[必要]{ひつよう:necessary}。ISMSは[組織]{そしき:organization}の[一部]{いちぶ:part}（[特定]{とくてい:specific}の[部門]{ぶもん:department}やサービス）を[対象]{たいしょう:scope}として[限定]{げんてい:limit}して[取得]{しゅとく:obtain}できる。",[316,317],"P-Mark","ISMS",{"id":319,"articleId":225,"question":320,"options":323,"correctLabel":21,"explanation":336,"tags":339},"kjh-mock-k2v5-q14",{"en":321,"jp":322},"Which activity falls under the \"Protect\" function of NIST CSF?","NIST CSFの「[防御]{ぼうぎょ:protect}（Protect）」に[該当]{がいとう:applicable}する[活動]{かつどう:activity}はどれか。",[324,327,330,333],{"label":17,"jp":325,"en":326},"[資産]{しさん:assets}の[特定]{とくてい:identification}とリスク[評価]{ひょうか:assessment}","Asset identification and risk assessment",{"label":21,"jp":328,"en":329},"アクセス[制御]{せいぎょ:control}と[従業者]{じゅうぎょうしゃ:employees}のセキュリティ[教育]{きょういく:education}","Access control and employee security education",{"label":25,"jp":331,"en":332},"セキュリティイベントの[監視]{かんし:monitoring}","Monitoring security events",{"label":29,"jp":334,"en":335},"インシデント[後]{ご:after}の[復旧]{ふっきゅう:recovery}[計画]{けいかく:planning}の[実行]{じっこう:execution}","Executing recovery plans after incidents",{"en":337,"jp":338},"\"Protect\" includes access control, employee security education, data protection, and maintenance management. A is \"Identify,\" C is \"Detect,\" D is \"Recover.\"","「[防御]{ぼうぎょ:protect}」にはアクセス[制御]{せいぎょ:control}、[従業者]{じゅうぎょうしゃ:employees}のセキュリティ[教育]{きょういく:education}、データ[保護]{ほご:protection}、[保守]{ほしゅ:maintenance}[管理]{かんり:management}などが[含]{ふく:included}まれる。アは「[識別]{しきべつ:identify}」、ウは「[検知]{けんち:detect}」、エは「[復旧]{ふっきゅう:recover}」。",[340],"NIST-CSF",{"id":342,"articleId":249,"question":343,"options":346,"correctLabel":25,"explanation":359,"tags":362},"kjh-mock-k2v5-q15",{"en":344,"jp":345},"What corresponds to \"C (Check)\" in the ISMS PDCA cycle?","ISMSにおけるPDCAサイクルの「C（Check）」に[該当]{がいとう:applicable}するものはどれか。",[347,350,353,356],{"label":17,"jp":348,"en":349},"セキュリティ[方針]{ほうしん:policy}の[策定]{さくてい:formulation}","Formulating security policy",{"label":21,"jp":351,"en":352},"セキュリティ[対策]{たいさく:measures}の[実施]{じっし:implementation}","Implementing security measures",{"label":25,"jp":354,"en":355},"[内部]{ないぶ:internal}[監査]{かんさ:audit}やマネジメントレビューによる[評価]{ひょうか:evaluation}","Evaluation through internal audits and management reviews",{"label":29,"jp":357,"en":358},"[改善]{かいぜん:improvement}[措置]{そち:measures}の[実行]{じっこう:execution}","Executing improvement measures",{"en":360,"jp":361},"C (Check) in the PDCA cycle evaluates and monitors ISMS operation through internal audits and management reviews. P is policy formulation, D is implementation, A is improvement.","PDCAサイクルのC（Check）は、[内部]{ないぶ:internal}[監査]{かんさ:audit}やマネジメントレビューを[通]{つう:through}じてISMSの[運用]{うんよう:operation}[状況]{じょうきょう:status}を[評価]{ひょうか:evaluate}・[監視]{かんし:monitor}する[段階]{だんかい:stage}。P（Plan）は[方針]{ほうしん:policy}[策定]{さくてい:formulation}、D（Do）は[実施]{じっし:implementation}、A（Act）は[改善]{かいぜん:improvement}。",[317,363],"ISO-27001",{"id":365,"articleId":366,"question":367,"options":370,"correctLabel":17,"explanation":383,"tags":386},"kjh-mock-k2v5-q16","kjh-k1-h04-anzen-kanri",{"en":368,"jp":369},"Why is the representative's signature included in the basic policy?","[基本方針]{きほんほうしん:basic policy}に[代表者]{だいひょうしゃ:representative}の[署名]{しょめい:signature}を[含]{ふく:include}める[理由]{りゆう:reason}はどれか。",[371,374,377,380],{"label":17,"jp":372,"en":373},"[経営]{けいえい:management}[層]{そう:level}の[責任]{せきにん:responsibility}と[関与]{かんよ:involvement}を[明確]{めいかく:clarify}にするため","To clarify management's responsibility and involvement",{"label":21,"jp":375,"en":376},"[書類]{しょるい:document}の[見栄]{みば:appearance}えをよくするため","To improve the document's appearance",{"label":25,"jp":378,"en":379},"[法律]{ほうりつ:law}で[署名]{しょめい:signature}の[書体]{しょたい:font}が[指定]{してい:specified}されているため","Because the law specifies the signature font",{"label":29,"jp":381,"en":382},"[印刷]{いんさつ:printing}コストを[削減]{さくげん:reduce}するため","To reduce printing costs",{"en":384,"jp":385},"Including the representative's signature demonstrates to internal and external parties that management takes responsibility for and is proactively involved in personal information protection.","[基本方針]{きほんほうしん:basic policy}に[代表者]{だいひょうしゃ:representative}の[署名]{しょめい:signature}を[含]{ふく:include}めることで、[経営]{けいえい:management}[層]{そう:level}が[個人情報]{こじんじょうほう:personal information}[保護]{ほご:protection}に[責任]{せきにん:responsibility}を[持]{も:have}ち、[積極的]{せっきょくてき:proactively}に[関与]{かんよ:involve}していることを[内外]{ないがい:internally\u002Fexternally}に[示]{しめ:demonstrate}す。",[387],"basic-policy",{"id":389,"articleId":390,"question":391,"options":394,"correctLabel":17,"explanation":407,"tags":410},"kjh-mock-k2v5-q17","kjh-k1-h11-my-number-hogo",{"en":392,"jp":393},"What is the purpose of setting \"retention period\" as a register item?","[管理]{かんり:management}[台帳]{だいちょう:register}の[項目]{こうもく:items}として「[保管]{ほかん:storage}[期間]{きかん:period}」を[設定]{せってい:set}する[目的]{もくてき:purpose}はどれか。",[395,398,401,404],{"label":17,"jp":396,"en":397},"[不要]{ふよう:unnecessary}になった[個人情報]{こじんじょうほう:personal information}を[適時]{てきじ:timely}に[消去]{しょうきょ:delete}し、[漏]{ろう:leak}えいリスクを[低減]{ていげん:reduce}する","Timely deleting unnecessary personal information to reduce leakage risk",{"label":21,"jp":399,"en":400},"データベースの[容量]{ようりょう:capacity}を[管理]{かんり:manage}する","Managing database capacity",{"label":25,"jp":402,"en":403},"[従業者]{じゅうぎょうしゃ:employees}の[勤続]{きんぞく:service}[年数]{ねんすう:years}を[把握]{はあく:grasp}する","Grasping employees' years of service",{"label":29,"jp":405,"en":406},"[印刷]{いんさつ:printing}[用紙]{ようし:paper}の[在庫]{ざいこ:inventory}を[管理]{かんり:manage}する","Managing printing paper inventory",{"en":408,"jp":409},"Setting retention periods enables timely deletion\u002Fdisposal of personal information that is no longer needed, reducing leakage risk. Personal information retention should be minimized.","[保管]{ほかん:storage}[期間]{きかん:period}を[設定]{せってい:set}することで、[利用]{りよう:use}[目的]{もくてき:purpose}を[達成]{たっせい:achieved}し[不要]{ふよう:unnecessary}になった[個人情報]{こじんじょうほう:personal information}を[適時]{てきじ:timely}に[消去]{しょうきょ:delete}・[廃棄]{はいき:dispose}し、[漏]{ろう:leak}えいリスクを[低減]{ていげん:reduce}する。[個人情報]{こじんじょうほう:personal information}の[保有]{ほゆう:retention}は[必要]{ひつよう:necessary}[最小限]{さいしょうげん:minimum}にすべき。",[411],"management-register",{"id":413,"articleId":414,"question":415,"options":418,"correctLabel":17,"explanation":431,"tags":434},"kjh-mock-k2v5-q18","kjh-k2-h02-soshiki-kiso",{"en":416,"jp":417},"What is an appropriate condition for \"risk acceptance\" in risk treatment?","リスク[対応]{たいおう:treatment}における「リスク[受容]{じゅよう:acceptance}」の[条件]{じょうけん:condition}として[適切]{てきせつ:appropriate}なものはどれか。",[419,422,425,428],{"label":17,"jp":420,"en":421},"リスクの[存在]{そんざい:existence}を[認識]{にんしき:recognize}した[上]{うえ:on}で、[対策]{たいさく:countermeasure}コストがリスクの[影響]{えいきょう:impact}を[上回]{うわまわ:exceed}る[場合]{ばあい:case}に[経営]{けいえい:management}[判断]{はんだん:judgment}として[受容]{じゅよう:accept}する","When the countermeasure cost exceeds the risk impact, accepting as a management judgment while recognizing the risk",{"label":21,"jp":423,"en":424},"リスクを[知]{し:know}らないので[何]{なに:anything}もしない","Doing nothing because the risk is unknown",{"label":25,"jp":426,"en":427},"[全]{すべ:all}てのリスクを[無条件]{むじょうけん:unconditionally}に[受容]{じゅよう:accept}する","Accepting all risks unconditionally",{"label":29,"jp":429,"en":430},"[担当者]{たんとうしゃ:person in charge}が[個人的]{こじんてき:personally}に[判断]{はんだん:judge}する","The person in charge judges personally",{"en":432,"jp":433},"Risk acceptance means recognizing the risk, comparing countermeasure cost and effectiveness, and management deciding to accept it. This differs from ignorance or neglect.","リスク[受容]{じゅよう:acceptance}は、リスクを[認識]{にんしき:recognize}した[上]{うえ:on}で、[対策]{たいさく:countermeasure}コストと[効果]{こうか:effectiveness}を[比較]{ひかく:compare}し、[経営]{けいえい:management}[層]{そう:level}が[判断]{はんだん:judge}して[受]{う:accept}け[入]{い:accept}れること。[無知]{むち:ignorance}や[放置]{ほうち:neglect}とは[異]{こと:different}なる。",[435],"risk-analysis",{"id":437,"articleId":414,"question":438,"options":441,"correctLabel":25,"explanation":454,"tags":457},"kjh-mock-k2v5-q19",{"en":439,"jp":440},"Which correctly arranges the three layers of the regulation document hierarchy from top?","[規程]{きてい:regulations}[文書]{ぶんしょ:documents}[体系]{たいけい:hierarchy}の3[層]{そう:layers}を[上位]{じょうい:upper}から[正]{ただ:correct}しく[並]{なら:arranged}べたものはどれか。",[442,445,448,451],{"label":17,"jp":443,"en":444},"[実施]{じっし:implementation}[手順書]{てじゅんしょ:procedures}→[対策]{たいさく:measures}[基準]{きじゅん:standards}→[基本方針]{きほんほうしん:basic policy}","Implementation procedures → Countermeasure standards → Basic policy",{"label":21,"jp":446,"en":447},"[基本方針]{きほんほうしん:basic policy}→[実施]{じっし:implementation}[手順書]{てじゅんしょ:procedures}→[対策]{たいさく:measures}[基準]{きじゅん:standards}","Basic policy → Implementation procedures → Countermeasure standards",{"label":25,"jp":449,"en":450},"[基本方針]{きほんほうしん:basic policy}→[対策]{たいさく:measures}[基準]{きじゅん:standards}→[実施]{じっし:implementation}[手順書]{てじゅんしょ:procedures}","Basic policy → Countermeasure standards → Implementation procedures",{"label":29,"jp":452,"en":453},"[対策]{たいさく:measures}[基準]{きじゅん:standards}→[基本方針]{きほんほうしん:basic policy}→[実施]{じっし:implementation}[手順書]{てじゅんしょ:procedures}","Countermeasure standards → Basic policy → Implementation procedures",{"en":455,"jp":456},"The hierarchy from top is: basic policy (organizational policy declaration) → countermeasure standards (specific criteria) → implementation procedures (operational steps).","[規程]{きてい:regulations}[文書]{ぶんしょ:documents}[体系]{たいけい:hierarchy}は[上位]{じょうい:upper}から、[基本方針]{きほんほうしん:basic policy}（[組織]{そしき:organization}の[方針]{ほうしん:policy}[宣言]{せんげん:declaration}）→[対策]{たいさく:measures}[基準]{きじゅん:standards}（[具体的]{ぐたいてき:specific}な[基準]{きじゅん:standards}）→[実施]{じっし:implementation}[手順書]{てじゅんしょ:procedures}（[操作]{そうさ:operation}[手順]{てじゅん:procedures}）。",[458],"document-hierarchy",{"id":460,"articleId":366,"question":461,"options":464,"correctLabel":17,"explanation":477,"tags":480},"kjh-mock-k2v5-q20",{"en":462,"jp":463},"Which is included in \"establishing an incident response structure\" in organizational safety management measures?","[組織的]{そしきてき:organizational}[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}の「[事案]{じあん:case}[対応]{たいおう:response}[体制]{たいせい:structure}の[整備]{せいび:establishment}」に[含]{ふく:include}まれるものはどれか。",[465,468,471,474],{"label":17,"jp":466,"en":467},"[漏]{ろう:leak}えい[等]{とう:etc.}の[事案]{じあん:case}が[発生]{はっせい:occur}した[際]{さい:when}の[報告]{ほうこく:reporting}[連絡]{れんらく:contact}[体制]{たいせい:structure}の[構築]{こうちく:construction}","Constructing a reporting\u002Fcontact structure for when leakage cases occur",{"label":21,"jp":469,"en":470},"[社員]{しゃいん:employee}[旅行]{りょこう:trip}の[企画]{きかく:planning}","Planning employee trips",{"label":25,"jp":472,"en":473},"[新商品]{しんしょうひん:new product}のマーケティング[戦略]{せんりゃく:strategy}","New product marketing strategy",{"label":29,"jp":475,"en":476},"オフィスの[内装]{ないそう:interior}デザイン","Office interior design",{"en":478,"jp":479},"Establishing an incident response structure includes reporting\u002Fcontact structures for leakage cases, initial response procedures, and notification procedures for related agencies.","[事案]{じあん:case}[対応]{たいおう:response}[体制]{たいせい:structure}の[整備]{せいび:establishment}には、[漏]{ろう:leak}えい[等]{とう:etc.}の[事案]{じあん:case}が[発生]{はっせい:occur}した[場合]{ばあい:case}の[報告]{ほうこく:reporting}[連絡]{れんらく:contact}[体制]{たいせい:structure}、[初動]{しょどう:initial}[対応]{たいおう:response}[手順]{てじゅん:procedures}、[関係]{かんけい:related}[機関]{きかん:agencies}への[通報]{つうほう:notification}[手順]{てじゅん:procedures}が[含]{ふく:included}まれる。",[481,482],"organizational-measures","incident-response",{"id":484,"articleId":485,"question":486,"options":489,"correctLabel":17,"explanation":502,"tags":505},"kjh-mock-k2v5-q21","kjh-k2-h02-anzen-kanri-sochi",{"en":487,"jp":488},"What should be done when an employee joins the company as a human safety management measure?","[人的]{じんてき:human}[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}として、[入社]{にゅうしゃ:joining company}[時]{じ:time}に[行]{おこな:carry out}うべきことはどれか。",[490,493,496,499],{"label":17,"jp":491,"en":492},"[秘密]{ひみつ:confidentiality}[保持]{ほじ:maintenance}に[関]{かん:related}する[誓約書]{せいやくしょ:pledge}の[取得]{しゅとく:acquisition}とセキュリティ[教育]{きょういく:education}の[実施]{じっし:implementation}","Obtaining a confidentiality pledge and conducting security education",{"label":21,"jp":494,"en":495},"[歓迎]{かんげい:welcome}[会]{かい:party}の[開催]{かいさい:holding}のみ","Only holding a welcome party",{"label":25,"jp":497,"en":498},"[名刺]{めいし:business cards}の[作成]{さくせい:creation}のみ","Only creating business cards",{"label":29,"jp":500,"en":501},"[特]{とく:particular}に[何]{なに:anything}もしなくてよい","Nothing in particular needs to be done",{"en":503,"jp":504},"When joining the company, a confidentiality pledge should be obtained and security education on personal information protection should be conducted.","[入社]{にゅうしゃ:joining}[時]{じ:time}には、[秘密]{ひみつ:confidentiality}[保持]{ほじ:maintenance}に[関]{かん:related}する[誓約書]{せいやくしょ:pledge}を[取得]{しゅとく:obtain}し、[個人情報]{こじんじょうほう:personal information}[保護]{ほご:protection}に[関]{かん:related}するセキュリティ[教育]{きょういく:education}を[実施]{じっし:conduct}する。",[506],"human-measures",{"id":508,"articleId":366,"question":509,"options":512,"correctLabel":21,"explanation":525,"tags":528},"kjh-mock-k2v5-q22",{"en":510,"jp":511},"Who bears the supervision responsibility for a dispatched employee's personal information handling?","[派遣]{はけん:dispatched}[社員]{しゃいん:employee}の[個人情報]{こじんじょうほう:personal information}[取扱]{とりあつかい:handling}いに[関]{かん:related}する[監督]{かんとく:supervision}[責任]{せきにん:responsibility}は[誰]{だれ:who}にあるか。",[513,516,519,522],{"label":17,"jp":514,"en":515},"[派遣]{はけん:dispatch}[元]{もと:source}の[会社]{かいしゃ:company}のみ","Only the dispatch source company",{"label":21,"jp":517,"en":518},"[派遣先]{はけんさき:dispatch destination}の[事業者]{じぎょうしゃ:operator}（[派遣]{はけん:dispatched}[社員]{しゃいん:employee}を[受]{う:receive}け[入]{い:accept}れている[側]{がわ:side}）","The dispatch destination operator (the side receiving the dispatched employee)",{"label":25,"jp":520,"en":521},"[派遣]{はけん:dispatched}[社員]{しゃいん:employee}[本人]{ほんにん:themselves}のみ","Only the dispatched employee themselves",{"label":29,"jp":523,"en":524},"[誰]{だれ:anyone}にも[責任]{せきにん:responsibility}はない","No one bears responsibility",{"en":526,"jp":527},"Dispatched employees are \"employees\" of the destination, and the destination operator bears supervision responsibility for personal information handling.","[派遣]{はけん:dispatched}[社員]{しゃいん:employee}は[派遣先]{はけんさき:destination}の「[従業者]{じゅうぎょうしゃ:employee}」に[該当]{がいとう:applicable}し、[派遣先]{はけんさき:destination}の[事業者]{じぎょうしゃ:operator}が[個人情報]{こじんじょうほう:personal information}の[取扱]{とりあつかい:handling}いについて[監督]{かんとく:supervision}[責任]{せきにん:responsibility}を[負]{お:bear}う。",[529],"employee-definition",{"id":531,"articleId":366,"question":532,"options":535,"correctLabel":17,"explanation":548,"tags":551},"kjh-mock-k2v5-q23",{"en":533,"jp":534},"Which correctly enumerates the three stages of subcontractor supervision?","[委託先]{いたくさき:subcontractor}[監督]{かんとく:supervision}の3つの[段階]{だんかい:stages}を[正]{ただ:correct}しく[列挙]{れっきょ:enumerate}したものはどれか。",[536,539,542,545],{"label":17,"jp":537,"en":538},"[選定]{せんてい:selection}→[契約]{けいやく:contract}→[運用]{うんよう:operation}（[監督]{かんとく:supervision}・[確認]{かくにん:verification}）","Selection → Contract → Operation (supervision\u002Fverification)",{"label":21,"jp":540,"en":541},"[契約]{けいやく:contract}→[選定]{せんてい:selection}→[評価]{ひょうか:evaluation}","Contract → Selection → Evaluation",{"label":25,"jp":543,"en":544},"[支払]{しはら:payment}い→[納品]{のうひん:delivery}→[検収]{けんしゅう:acceptance}","Payment → Delivery → Acceptance",{"label":29,"jp":546,"en":547},"[企画]{きかく:planning}→[開発]{かいはつ:development}→[運用]{うんよう:operation}","Planning → Development → Operation",{"en":549,"jp":550},"Subcontractor supervision is conducted in 3 stages: (1) selection (verifying safety management level) → (2) contract (stipulating confidentiality, sub-subcontracting restrictions, etc.) → (3) operation (periodic supervision\u002Fverification).","[委託先]{いたくさき:subcontractor}[監督]{かんとく:supervision}は、①[選定]{せんてい:selection}（[安全]{あんぜん:safety}[管理]{かんり:management}[水準]{すいじゅん:level}の[確認]{かくにん:verification}）→②[契約]{けいやく:contract}（[秘密]{ひみつ:confidentiality}[保持]{ほじ:maintenance}、[再委託]{さいいたく:sub-subcontracting}[制限]{せいげん:restrictions}等の[規定]{きてい:stipulation}）→③[運用]{うんよう:operation}（[定期的]{ていきてき:periodic}な[監督]{かんとく:supervision}・[確認]{かくにん:verification}）の3[段階]{だんかい:stages}で[行]{おこな:conduct}う。",[552],"subcontractor-supervision",{"id":554,"articleId":555,"question":556,"options":559,"correctLabel":17,"explanation":572,"tags":575},"kjh-mock-k2v5-q24","kjh-k1-h04-daisan-sha-teikyou",{"en":557,"jp":558},"What does \"prohibition of use beyond purpose\" established in outsourcing contracts mean?","[委託]{いたく:outsourcing}[契約]{けいやく:contract}で[定]{さだ:establish}める「[目的外]{もくてきがい:beyond purpose}[利用]{りよう:use}の[禁止]{きんし:prohibition}」の[意味]{いみ:meaning}はどれか。",[560,563,566,569],{"label":17,"jp":561,"en":562},"[委託]{いたく:outsourced}された[業務]{ぎょうむ:operations}の[範囲]{はんい:scope}[外]{がい:outside}で[個人]{こじん:personal}データを[利用]{りよう:use}してはならない","Personal data must not be used outside the scope of outsourced operations",{"label":21,"jp":564,"en":565},"[委託先]{いたくさき:subcontractor}は[自由]{じゆう:freely}に[個人]{こじん:personal}データを[利用]{りよう:use}できる","The subcontractor can freely use personal data",{"label":25,"jp":567,"en":568},"[委託元]{いたくもと:outsourcer}は[委託先]{いたくさき:subcontractor}のデータを[自由]{じゆう:freely}に[利用]{りよう:use}できる","The outsourcer can freely use the subcontractor's data",{"label":29,"jp":570,"en":571},"[個人]{こじん:personal}データの[利用]{りよう:use}に[制限]{せいげん:restrictions}はない","There are no restrictions on personal data use",{"en":573,"jp":574},"\"Prohibition of use beyond purpose\" prohibits the subcontractor from using received personal data beyond the scope necessary for performing the outsourced operations.","「[目的外]{もくてきがい:beyond purpose}[利用]{りよう:use}の[禁止]{きんし:prohibition}」は、[委託先]{いたくさき:subcontractor}が[受]{う:received}け[取]{と:received}った[個人]{こじん:personal}データを、[委託]{いたく:outsourced}[業務]{ぎょうむ:operations}の[遂行]{すいこう:performance}に[必要]{ひつよう:necessary}な[範囲]{はんい:scope}を[超]{こ:exceed}えて[利用]{りよう:use}することを[禁止]{きんし:prohibit}するもの。",[576],"subcontractor-contract",{"id":578,"articleId":366,"question":579,"options":582,"correctLabel":17,"explanation":595,"tags":598},"kjh-mock-k2v5-q25",{"en":580,"jp":581},"Why is \"notification to the person\" required in leakage incident response?","[漏]{ろう:leak}えい[事故]{じこ:incident}の[対応]{たいおう:response}で「[本人]{ほんにん:person}への[通知]{つうち:notification}」が[必要]{ひつよう:necessary}とされる[理由]{りゆう:reason}はどれか。",[583,586,589,592],{"label":17,"jp":584,"en":585},"[本人]{ほんにん:person}が[二次]{にじ:secondary}[被害]{ひがい:damage}を[防]{ふせ:prevent}ぐための[措置]{そち:measures}を[講]{こう:take}じられるようにするため","So the person can take measures to prevent secondary damage",{"label":21,"jp":587,"en":588},"マスコミ[対応]{たいおう:response}のため","For media response",{"label":25,"jp":590,"en":591},"[法的]{ほうてき:legal}な[義務]{ぎむ:obligation}はないが[慣例]{かんれい:custom}として","Not a legal obligation but as custom",{"label":29,"jp":593,"en":594},"[通知]{つうち:notification}は[不要]{ふよう:unnecessary}","Notification is unnecessary",{"en":596,"jp":597},"Notification enables the person to prevent secondary damage (identity theft, unauthorized use, etc.) from leaked personal information. It is mandatory under the Personal Information Protection Act.","[本人]{ほんにん:person}への[通知]{つうち:notification}は、[漏]{ろう:leaked}えいした[個人情報]{こじんじょうほう:personal information}を[悪用]{あくよう:exploit}した[二次]{にじ:secondary}[被害]{ひがい:damage}（なりすまし、[不正]{ふせい:unauthorized}[利用]{りよう:use}など）を[本人]{ほんにん:person}が[防]{ふせ:prevent}げるようにするための[措置]{そち:measure}。[個人情報]{こじんじょうほう:personal information}[保護法]{ほごほう:protection act}で[義務化]{ぎむか:mandatory}されている。",[482],{"id":600,"articleId":366,"question":601,"options":604,"correctLabel":17,"explanation":617,"tags":620},"kjh-mock-k2v5-q26",{"en":602,"jp":603},"What should the subcontractor report to the outsourcer when sub-subcontracting?","[再委託]{さいいたく:sub-subcontracting}を[行]{おこな:carry out}う[際]{さい:when}、[委託先]{いたくさき:subcontractor}が[委託元]{いたくもと:outsourcer}に[報告]{ほうこく:report}すべき[事項]{じこう:items}はどれか。",[605,608,611,614],{"label":17,"jp":606,"en":607},"[再委託先]{さいいたくさき:sub-subcontractor}の[名称]{めいしょう:name}、[取扱]{とりあつかい:handling}い[範囲]{はんい:scope}、[安全]{あんぜん:safety}[管理]{かんり:management}[体制]{たいせい:structure}","Sub-subcontractor name, handling scope, safety management structure",{"label":21,"jp":609,"en":610},"[再委託先]{さいいたくさき:sub-subcontractor}の[社員]{しゃいん:employees}の[趣味]{しゅみ:hobbies}","Sub-subcontractor employees' hobbies",{"label":25,"jp":612,"en":613},"[報告]{ほうこく:reporting}は[不要]{ふよう:unnecessary}","Reporting is unnecessary",{"label":29,"jp":615,"en":616},"[再委託先]{さいいたくさき:sub-subcontractor}の[株価]{かぶか:stock price}","Sub-subcontractor's stock price",{"en":618,"jp":619},"When sub-subcontracting, the sub-subcontractor's name, personal data handling scope, and safety management structure must be reported to the outsourcer for approval.","[再委託]{さいいたく:sub-subcontracting}の[際]{さい:when}は、[再委託先]{さいいたくさき:sub-subcontractor}の[名称]{めいしょう:name}、[個人]{こじん:personal}データの[取扱]{とりあつかい:handling}い[範囲]{はんい:scope}、[安全]{あんぜん:safety}[管理]{かんり:management}[体制]{たいせい:structure}を[委託元]{いたくもと:outsourcer}に[報告]{ほうこく:report}し、[承認]{しょうにん:approval}を[得]{え:obtain}る[必要]{ひつよう:need}がある。",[621],"sub-subcontracting",{"id":623,"articleId":414,"question":624,"options":627,"correctLabel":17,"explanation":640,"tags":643},"kjh-mock-k2v5-q27",{"en":625,"jp":626},"Which effort should be utilized for improving complaint response?","[苦情]{くじょう:complaint}[対応]{たいおう:response}の[改善]{かいぜん:improvement}に[活]{い:utilize}かすべき[取]{と:effort}り[組]{く:effort}みはどれか。",[628,631,634,637],{"label":17,"jp":629,"en":630},"[苦情]{くじょう:complaint}[内容]{ないよう:content}を[分析]{ぶんせき:analyze}し、[個人情報]{こじんじょうほう:personal information}[保護]{ほご:protection}[体制]{たいせい:structure}の[改善]{かいぜん:improvement}に[反映]{はんえい:reflect}する","Analyzing complaint content and reflecting it in improving the personal information protection structure",{"label":21,"jp":632,"en":633},"[苦情]{くじょう:complaints}を[無視]{むし:ignore}する","Ignoring complaints",{"label":25,"jp":635,"en":636},"[苦情]{くじょう:complaint}[件数]{けんすう:number}のみを[集計]{しゅうけい:aggregate}する","Only aggregating complaint numbers",{"label":29,"jp":638,"en":639},"[苦情]{くじょう:complaint}[窓口]{まどぐち:contact point}を[閉鎖]{へいさ:close}する","Closing the complaint contact point",{"en":641,"jp":642},"Analyzing complaint content, identifying causes, and using them to improve the PI protection structure is important. Complaints are an important information source for the \"C\" in the PDCA cycle.","[苦情]{くじょう:complaint}[内容]{ないよう:content}を[分析]{ぶんせき:analyze}し、[原因]{げんいん:causes}を[特定]{とくてい:identify}して[個人情報]{こじんじょうほう:personal information}[保護]{ほご:protection}[体制]{たいせい:structure}の[改善]{かいぜん:improvement}に[活]{い:utilize}かすことが[重要]{じゅうよう:important}。[苦情]{くじょう:complaints}はPDCAサイクルの「C」の[重要]{じゅうよう:important}な[情報]{じょうほう:information}[源]{げん:source}。",[644],"complaint-handling",{"id":646,"articleId":366,"question":647,"options":650,"correctLabel":17,"explanation":663,"tags":666},"kjh-mock-k2v5-q28",{"en":648,"jp":649},"What should be clarified in \"structure establishment\" of organizational safety management measures?","[組織的]{そしきてき:organizational}[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}の「[体制]{たいせい:structure}[整備]{せいび:establishment}」で[明確]{めいかく:clarify}にすべきことはどれか。",[651,654,657,660],{"label":17,"jp":652,"en":653},"[個人情報]{こじんじょうほう:personal information}[保護]{ほご:protection}の[責任者]{せきにんしゃ:responsible person}と[担当者]{たんとうしゃ:persons in charge}の[役割]{やくわり:roles}・[責任]{せきにん:responsibilities}","Roles and responsibilities of PI protection responsible persons and persons in charge",{"label":21,"jp":655,"en":656},"[社員]{しゃいん:employees}の[座席]{ざせき:seating}[表]{ひょう:chart}","Employee seating chart",{"label":25,"jp":658,"en":659},"[社内]{しゃない:internal}イベントの[日程]{にってい:schedule}","Internal event schedule",{"label":29,"jp":661,"en":662},"[駐車場]{ちゅうしゃじょう:parking lot}の[利用]{りよう:usage}ルール","Parking lot usage rules",{"en":664,"jp":665},"\"Structure establishment\" involves appointing a PI protection manager and persons in charge, clarifying roles and responsibilities, and establishing reporting routes.","「[体制]{たいせい:structure}[整備]{せいび:establishment}」では、[個人情報]{こじんじょうほう:personal information}[保護]{ほご:protection}[管理者]{かんりしゃ:manager}、[担当者]{たんとうしゃ:persons in charge}の[設置]{せっち:appointment}、[役割]{やくわり:roles}と[責任]{せきにん:responsibilities}の[明確化]{めいかくか:clarification}、[報告]{ほうこく:reporting}[経路]{けいろ:routes}の[確立]{かくりつ:establishment}を[行]{おこな:conduct}う。",[481],{"id":668,"articleId":225,"question":669,"options":672,"correctLabel":29,"explanation":685,"tags":688},"kjh-mock-k2v5-q29",{"en":670,"jp":671},"Which is NOT included in the four risk analysis methods?","リスク[分析]{ぶんせき:analysis}の4[手法]{しゅほう:methods}に[含]{ふく:include}まれないものはどれか。",[673,676,679,682],{"label":17,"jp":674,"en":675},"ベースラインアプローチ","Baseline approach",{"label":21,"jp":677,"en":678},"[詳細]{しょうさい:detailed}リスク[分析]{ぶんせき:analysis}","Detailed risk analysis",{"label":25,"jp":680,"en":681},"[非]{ひ:in-}[形式的]{けいしきてき:formal}アプローチ","Informal approach",{"label":29,"jp":683,"en":684},"ウォーターフォールアプローチ","Waterfall approach",{"en":686,"jp":687},"The 4 risk analysis methods are: baseline, detailed, informal, and combined approaches. Waterfall is a software development methodology, not a risk analysis method.","リスク[分析]{ぶんせき:analysis}の4[手法]{しゅほう:methods}は、①ベースラインアプローチ、②[詳細]{しょうさい:detailed}リスク[分析]{ぶんせき:analysis}、③[非]{ひ:in-}[形式的]{けいしきてき:formal}アプローチ、④[組]{く:combination}み[合]{あ:together}わせアプローチ。ウォーターフォールはソフトウェア[開発]{かいはつ:development}[手法]{しゅほう:methodology}であり、リスク[分析]{ぶんせき:analysis}の[手法]{しゅほう:method}ではない。",[435],{"id":690,"articleId":366,"question":691,"options":694,"correctLabel":25,"explanation":707,"tags":710},"kjh-mock-k2v5-q30",{"en":692,"jp":693},"Which falls under \"physical safety management measures\" among the four categories?","[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}の4[分類]{ぶんるい:categories}のうち、「[物理的]{ぶつりてき:physical}[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}」に[該当]{がいとう:applicable}するものはどれか。",[695,698,701,704],{"label":17,"jp":696,"en":697},"[従業者]{じゅうぎょうしゃ:employees}へのセキュリティ[研修]{けんしゅう:training}","Security training for employees",{"label":21,"jp":699,"en":700},"アクセス[制御]{せいぎょ:control}ソフトの[導入]{どうにゅう:introduction}","Introducing access control software",{"label":25,"jp":702,"en":703},"[管理]{かんり:managed}[区域]{くいき:zone}への[入退室]{にゅうたいしつ:entry\u002Fexit}[管理]{かんり:management}","Entry\u002Fexit management for managed zones",{"label":29,"jp":705,"en":706},"[規程]{きてい:regulations}の[策定]{さくてい:formulation}","Formulating regulations",{"en":708,"jp":709},"Physical measures include managed\u002Fhandling zone management, entry\u002Fexit management, equipment theft prevention, and media disposal. A is human, B is technical, D is organizational.","[物理的]{ぶつりてき:physical}[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}には、[管理]{かんり:managed}[区域]{くいき:zone}・[取扱]{とりあつかい:handling}[区域]{くいき:zone}の[管理]{かんり:management}、[入退室]{にゅうたいしつ:entry\u002Fexit}[管理]{かんり:management}、[機器]{きき:equipment}の[盗難]{とうなん:theft}[防止]{ぼうし:prevention}、[媒体]{ばいたい:media}の[廃棄]{はいき:disposal}が[含]{ふく:included}まれる。アは[人的]{じんてき:human}、イは[技術的]{ぎじゅつてき:technical}、エは[組織的]{そしきてき:organizational}[措置]{そち:measures}。",[711],"physical-measures",{"id":713,"articleId":714,"question":715,"options":718,"correctLabel":29,"explanation":731,"tags":734},"kjh-mock-k2v5-q31","kjh-k2-h03-office",{"en":716,"jp":717},"Which zone has the lowest security level in security zoning?","セキュリティゾーニングで[最]{もっと:most}も[低]{ひく:low}いセキュリティレベルの[区域]{くいき:zone}はどれか。",[719,722,725,728],{"label":17,"jp":720,"en":721},"サーバルーム","Server room",{"label":21,"jp":723,"en":724},"[金庫室]{きんこしつ:vault room}","Vault room",{"label":25,"jp":726,"en":727},"[一般]{いっぱん:general}[執務]{しつむ:work}エリア","General work area",{"label":29,"jp":729,"en":730},"[公開]{こうかい:public}[区域]{くいき:zone}（ロビー・[受付]{うけつけ:reception}）","Public zone (lobby\u002Freception)",{"en":732,"jp":733},"The public zone (lobby\u002Freception) has the lowest security level as external people can enter freely. Server rooms and vault rooms have the highest level.","[公開]{こうかい:public}[区域]{くいき:zone}（ロビー・[受付]{うけつけ:reception}）は[外部]{がいぶ:external}の[人]{ひと:people}が[自由]{じゆう:freely}に[出入]{でい:enter\u002Fexit}りできるため、セキュリティレベルが[最]{もっと:most}も[低]{ひく:low}い。サーバルーム・[金庫室]{きんこしつ:vault room}は[最]{もっと:most}も[高]{たか:high}い。",[735],"security-zoning",{"id":737,"articleId":738,"question":739,"options":742,"correctLabel":17,"explanation":755,"tags":758},"kjh-mock-k2v5-q32","kjh-k1-h11-my-number-sousoku",{"en":740,"jp":741},"What response should be taken for visitors in entry\u002Fexit management?","[入退室]{にゅうたいしつ:entry\u002Fexit}[管理]{かんり:management}で[来訪者]{らいほうしゃ:visitor}に[対]{たい:for}して[行]{おこな:carry out}うべき[対応]{たいおう:response}はどれか。",[743,746,749,752],{"label":17,"jp":744,"en":745},"[来訪者]{らいほうしゃ:visitor}[記録]{きろく:record}の[作成]{さくせい:creation}、[来訪者]{らいほうしゃ:visitor}バッジの[発行]{はっこう:issuance}、[社員]{しゃいん:employee}の[同行]{どうこう:accompaniment}","Creating visitor records, issuing visitor badges, employee accompaniment",{"label":21,"jp":747,"en":748},"[来訪者]{らいほうしゃ:visitors}に[社員]{しゃいん:employee}IDカードを[貸与]{たいよ:lend}する","Lending employee ID cards to visitors",{"label":25,"jp":750,"en":751},"[来訪者]{らいほうしゃ:visitors}を[自由]{じゆう:freely}に[出入]{でい:enter\u002Fexit}りさせる","Letting visitors enter\u002Fexit freely",{"label":29,"jp":753,"en":754},"[来訪者]{らいほうしゃ:visitor}[記録]{きろく:records}は[不要]{ふよう:unnecessary}","Visitor records are unnecessary",{"en":756,"jp":757},"For visitors: create records, issue visitor badges (to distinguish from employees), and have employee accompaniment. Lending employee IDs is inappropriate.","[来訪者]{らいほうしゃ:visitors}に[対]{たい:for}しては、[来訪者]{らいほうしゃ:visitor}[記録]{きろく:record}の[作成]{さくせい:creation}、[来訪者]{らいほうしゃ:visitor}バッジの[発行]{はっこう:issuance}（[社員]{しゃいん:employee}と[区別]{くべつ:distinguish}するため）、[社員]{しゃいん:employee}の[同行]{どうこう:accompaniment}を[行]{おこな:carry out}う。[社員]{しゃいん:employee}IDの[貸与]{たいよ:lending}は[不適切]{ふてきせつ:inappropriate}。",[759],"entry-exit-management",{"id":761,"articleId":366,"question":762,"options":765,"correctLabel":17,"explanation":778,"tags":781},"kjh-mock-k2v5-q33",{"en":763,"jp":764},"What is commonly required in both handling and managed zones?","[取扱]{とりあつかい:handling}[区域]{くいき:zone}と[管理]{かんり:managed}[区域]{くいき:zone}の[両方]{りょうほう:both}に[共通]{きょうつう:common}して[求]{もと:required}められることはどれか。",[766,769,772,775],{"label":17,"jp":767,"en":768},"[権限]{けんげん:authorized}のない[者]{もの:persons}による[個人]{こじん:personal}データへのアクセスを[防止]{ぼうし:prevent}する[措置]{そち:measures}","Measures preventing unauthorized persons from accessing personal data",{"label":21,"jp":770,"en":771},"[生体]{せいたい:biometric}[認証]{にんしょう:authentication}の[導入]{どうにゅう:introduction}","Introduction of biometric authentication",{"label":25,"jp":773,"en":774},"24[時間]{じかん:hours}[警備]{けいび:security}[員]{いん:guard}の[配置]{はいち:placement}","Placing a 24-hour security guard",{"label":29,"jp":776,"en":777},"[監視]{かんし:surveillance}カメラの[設置]{せっち:installation}","Installing surveillance cameras",{"en":779,"jp":780},"Both handling and managed zones require measures preventing unauthorized persons from accessing personal data. Specific methods differ by zone type.","[取扱]{とりあつかい:handling}[区域]{くいき:zone}も[管理]{かんり:managed}[区域]{くいき:zone}も、[権限]{けんげん:authorized}のない[者]{もの:persons}による[個人]{こじん:personal}データへのアクセスを[防止]{ぼうし:prevent}する[措置]{そち:measures}が[求]{もと:required}められる。[具体的]{ぐたいてき:specific}な[方法]{ほうほう:methods}は[区域]{くいき:zone}の[種類]{しゅるい:type}により[異]{こと:differ}なる。",[711,782],"zoning",{"id":784,"articleId":785,"question":786,"options":789,"correctLabel":17,"explanation":802,"tags":805},"kjh-mock-k2v5-q34","kjh-k2-h04-gijutsu-jisshi",{"en":787,"jp":788},"Why is restricting USB memory use recommended?","USBメモリの[利用]{りよう:use}[制限]{せいげん:restriction}が[推奨]{すいしょう:recommended}される[理由]{りゆう:reason}はどれか。",[790,793,796,799],{"label":17,"jp":791,"en":792},"[小型]{こがた:small}で[紛失]{ふんしつ:loss}しやすく、[大量]{たいりょう:large amount}のデータを[持]{も:carry}ち[出]{だ:out}せるため[漏]{ろう:leak}えいリスクが[高]{たか:high}い","Small size makes it easy to lose, and large data can be carried out, posing high leakage risk",{"label":21,"jp":794,"en":795},"USBメモリは[高価]{こうか:expensive}であるため","Because USB memory is expensive",{"label":25,"jp":797,"en":798},"USBメモリは[読取]{よみと:read}り[速度]{そくど:speed}が[遅]{おそ:slow}いため","Because USB memory read speed is slow",{"label":29,"jp":800,"en":801},"USBメモリは[容量]{ようりょう:capacity}が[少]{すく:little}ないため","Because USB memory has little capacity",{"en":803,"jp":804},"USB memory is small and portable but has high loss\u002Ftheft risk and can carry large amounts of personal data, so usage restriction and data encryption are recommended.","USBメモリは[小型]{こがた:small}で[携帯]{けいたい:portable}しやすいが、[紛失]{ふんしつ:loss}・[盗難]{とうなん:theft}のリスクが[高]{たか:high}く、[大量]{たいりょう:large amount}の[個人]{こじん:personal}データを[持]{も:carry}ち[出]{だ:out}せるため、[利用]{りよう:use}[制限]{せいげん:restriction}やデータ[暗号化]{あんごうか:encryption}が[推奨]{すいしょう:recommended}される。",[806,711],"data-erasure",{"id":808,"articleId":11,"question":809,"options":812,"correctLabel":17,"explanation":825,"tags":828},"kjh-mock-k2v5-q35",{"en":810,"jp":811},"Which correctly describes the relationship between BCP and DR plan?","BCPとDRプランの[関係]{かんけい:relationship}として[正]{ただ:correct}しいものはどれか。",[813,816,819,822],{"label":17,"jp":814,"en":815},"DRプランはBCPの[一部]{いちぶ:part}であり、IT[環境]{かんきょう:environment}の[復旧]{ふっきゅう:recovery}に[焦点]{しょうてん:focus}を[当]{あ:focus}てたもの","DR plan is a part of BCP, focusing on IT environment recovery",{"label":21,"jp":817,"en":818},"BCPとDRプランは[同]{おな:same}じもの","BCP and DR plan are the same thing",{"label":25,"jp":820,"en":821},"BCPはDRプランの[一部]{いちぶ:part}","BCP is a part of DR plan",{"label":29,"jp":823,"en":824},"[両者]{りょうしゃ:both}は[無関係]{むかんけい:unrelated}","Both are unrelated",{"en":826,"jp":827},"BCP covers overall business continuity. DR plan (disaster recovery plan) is a part of BCP, specifically focusing on IT environment recovery.","BCPは[事業]{じぎょう:business}[全体]{ぜんたい:entire}の[継続]{けいぞく:continuity}を[対象]{たいしょう:scope}とする[計画]{けいかく:plan}。DRプラン（[災害]{さいがい:disaster}[復旧]{ふっきゅう:recovery}[計画]{けいかく:plan}）はBCPの[一部]{いちぶ:part}であり、[特]{とく:particular}にIT[環境]{かんきょう:environment}の[復旧]{ふっきゅう:recovery}に[焦点]{しょうてん:focus}を[当]{あ:focus}てたもの。",[829],"BCP",{"id":831,"articleId":714,"question":832,"options":835,"correctLabel":21,"explanation":848,"tags":851},"kjh-mock-k2v5-q36",{"en":833,"jp":834},"Which technology helps bring RPO close to zero?","RPOを0に[近]{ちか:close}づけるための[技術]{ぎじゅつ:technology}はどれか。",[836,839,842,845],{"label":17,"jp":837,"en":838},"[週次]{しゅうじ:weekly}フルバックアップ","Weekly full backup",{"label":21,"jp":840,"en":841},"リアルタイムレプリケーション","Real-time replication",{"label":25,"jp":843,"en":844},"[月次]{げつじ:monthly}[差分]{さぶん:differential}バックアップ","Monthly differential backup",{"label":29,"jp":846,"en":847},"テープバックアップ","Tape backup",{"en":849,"jp":850},"Real-time replication immediately copies data, bringing RPO close to zero. Weekly or monthly backups result in longer RPOs.","リアルタイムレプリケーション（[同期]{どうき:synchronous}[複製]{ふくせい:replication}）は、データを[即時]{そくじ:immediately}に[複製]{ふくせい:replicate}するため、RPOを[限]{かぎ:limit}りなく0に[近]{ちか:close}づけることができる。[週次]{しゅうじ:weekly}や[月次]{げつじ:monthly}のバックアップではRPOは[長]{なが:long}くなる。",[829,852],"RPO",{"id":854,"articleId":249,"question":855,"options":858,"correctLabel":17,"explanation":871,"tags":874},"kjh-mock-k2v5-q37",{"en":856,"jp":857},"Which is a measure to shorten RTO?","RTOを[短縮]{たんしゅく:shorten}するための[対策]{たいさく:measure}はどれか。",[859,862,865,868],{"label":17,"jp":860,"en":861},"ホットサイトの[構築]{こうちく:construction}","Constructing a hot site",{"label":21,"jp":863,"en":864},"パスワードの[複雑化]{ふくざつか:complexity}","Making passwords more complex",{"label":25,"jp":866,"en":867},"[社員]{しゃいん:employee}[教育]{きょういく:education}の[強化]{きょうか:strengthening}","Strengthening employee education",{"label":29,"jp":869,"en":870},"[苦情]{くじょう:complaint}[窓口]{まどぐち:contact point}の[設置]{せっち:establishment}","Establishing a complaint contact point",{"en":872,"jp":873},"A hot site with constant standby and immediate switchover significantly shortens RTO. Password complexity and education are not directly related to shortening RTO.","ホットサイトは[常時]{じょうじ:constantly}[待機]{たいき:standby}で[即時]{そくじ:immediate}[切替]{きりかえ:switchover}[可能]{かのう:possible}なため、RTO（[復旧]{ふっきゅう:recovery}[時間]{じかん:time}[目標]{もくひょう:objective}）を[大幅]{おおはば:significantly}に[短縮]{たんしゅく:shorten}できる。パスワード[複雑化]{ふくざつか:complexity}や[教育]{きょういく:education}はRTOの[短縮]{たんしゅく:shortening}とは[直接]{ちょくせつ:direct}[関係]{かんけい:relationship}しない。",[829,875,876],"RTO","DR-site",{"id":878,"articleId":714,"question":879,"options":882,"correctLabel":17,"explanation":895,"tags":898},"kjh-mock-k2v5-q38",{"en":880,"jp":881},"In which situation is the clear desk\u002Fclear screen policy especially important?","クリアデスク・クリアスクリーンポリシーが[特]{とく:especially}に[重要]{じゅうよう:important}となる[場面]{ばめん:situation}はどれか。",[883,886,889,892],{"label":17,"jp":884,"en":885},"[来客]{らいきゃく:visitors}や[清掃]{せいそう:cleaning}[業者]{ぎょうしゃ:workers}が[執務]{しつむ:work}エリアに[入]{はい:enter}る[場合]{ばあい:case}","When visitors or cleaning workers enter the work area",{"label":21,"jp":887,"en":888},"[社員]{しゃいん:employees}[全員]{ぜんいん:everyone}がオフィスにいる[場合]{ばあい:case}","When all employees are in the office",{"label":25,"jp":890,"en":891},"[昼食]{ちゅうしょく:lunch}[時間]{じかん:time}のみ","Only during lunch time",{"label":29,"jp":893,"en":894},"[月曜日]{げつようび:Monday}のみ","Only on Mondays",{"en":896,"jp":897},"Clear desk\u002Fscreen is especially important when third parties like visitors or cleaning workers enter the work area. It should also always be implemented when leaving the office or seat.","クリアデスク・クリアスクリーンは、[来客]{らいきゃく:visitors}や[清掃]{せいそう:cleaning}[業者]{ぎょうしゃ:workers}など[第三者]{だいさんしゃ:third parties}が[執務]{しつむ:work}エリアに[入]{はい:enter}る[場合]{ばあい:case}に[特]{とく:especially}に[重要]{じゅうよう:important}。[退社]{たいしゃ:leaving office}[時]{じ:time}や[離席]{りせき:leaving seat}[時]{じ:time}も[常]{つね:always}に[実施]{じっし:implement}すべき。",[899],"clear-desk-screen",{"id":901,"articleId":11,"question":902,"options":905,"correctLabel":17,"explanation":918,"tags":921},"kjh-mock-k2v5-q39",{"en":903,"jp":904},"Which is the most effective theft countermeasure for a portable PC?","[持]{も:carry}ち[出]{だ:out}し[用]{よう:for}PCの[盗難]{とうなん:theft}[対策]{たいさく:countermeasure}として[最]{もっと:most}も[効果的]{こうかてき:effective}なものはどれか。",[906,909,912,915],{"label":17,"jp":907,"en":908},"ハードディスクの[全体]{ぜんたい:full}[暗号化]{あんごうか:encryption}","Full hard disk encryption",{"label":21,"jp":910,"en":911},"デスクトップの[壁紙]{かべがみ:wallpaper}を[変更]{へんこう:change}する","Changing the desktop wallpaper",{"label":25,"jp":913,"en":914},"PCの[色]{いろ:color}を[目立]{めだ:conspicuous}つものにする","Making the PC a conspicuous color",{"label":29,"jp":916,"en":917},"PCに[ステッカー]{すてっかー:sticker}を[貼]{は:attach}る","Attaching stickers to the PC",{"en":919,"jp":920},"Portable PCs have high theft\u002Floss risk, so full hard disk encryption is most effective to prevent data access even if stolen.","[持]{も:carry}ち[出]{だ:out}し[用]{よう:for}PCは[盗難]{とうなん:theft}・[紛失]{ふんしつ:loss}のリスクが[高]{たか:high}いため、ハードディスクの[全体]{ぜんたい:full}[暗号化]{あんごうか:encryption}により、[盗難]{とうなん:stolen}されてもデータへのアクセスを[防]{ふせ:prevent}ぐことが[最]{もっと:most}も[効果的]{こうかてき:effective}。",[711],{"id":923,"articleId":414,"question":924,"options":927,"correctLabel":29,"explanation":940,"tags":943},"kjh-mock-k2v5-q40",{"en":925,"jp":926},"Which is NOT an appropriate method for safely disposing of paper-based personal information?","[紙]{かみ:paper}[媒体]{ばいたい:media}の[個人情報]{こじんじょうほう:personal information}を[安全]{あんぜん:safely}に[廃棄]{はいき:dispose}する[方法]{ほうほう:method}として[適切]{てきせつ:appropriate}でないものはどれか。",[928,931,934,937],{"label":17,"jp":929,"en":930},"シュレッダーでの[裁断]{さいだん:shredding}","Shredding with a shredder",{"label":21,"jp":932,"en":933},"[溶解]{ようかい:dissolution}[処理]{しょり:processing}","Dissolution processing",{"label":25,"jp":935,"en":936},"[焼却]{しょうきゃく:incineration}[処理]{しょり:processing}","Incineration processing",{"label":29,"jp":938,"en":939},"[一般]{いっぱん:general}ごみとしてそのまま[廃棄]{はいき:disposal}","Disposal as general waste as-is",{"en":941,"jp":942},"Paper with personal information should be disposed of by methods making recovery impossible: shredding, dissolution, or incineration. Disposal as general waste poses leakage risk.","[個人情報]{こじんじょうほう:personal information}が[記載]{きさい:written}された[紙]{かみ:paper}[媒体]{ばいたい:media}は、シュレッダー、[溶解]{ようかい:dissolution}、[焼却]{しょうきゃく:incineration}など[復元]{ふくげん:recovery}[不可能]{ふかのう:impossible}な[方法]{ほうほう:method}で[廃棄]{はいき:dispose}すべき。[一般]{いっぱん:general}ごみとしてそのまま[廃棄]{はいき:dispose}すると[漏]{ろう:leak}えいリスクがある。",[806],{"id":945,"articleId":109,"question":946,"options":949,"correctLabel":21,"explanation":962,"tags":965},"kjh-mock-k2v5-q41",{"en":947,"jp":948},"What type of encryption algorithm is RSA?","RSAは[何]{なん:what}[方式]{ほうしき:method}の[暗号]{あんごう:cipher}アルゴリズムか。",[950,953,956,959],{"label":17,"jp":951,"en":952},"[共通鍵]{きょうつうかぎ:symmetric key}[暗号]{あんごう:cipher}","Symmetric-key cipher",{"label":21,"jp":954,"en":955},"[公開鍵]{こうかいかぎ:public key}[暗号]{あんごう:cipher}","Public-key cipher",{"label":25,"jp":957,"en":958},"ハッシュ[関数]{かんすう:function}","Hash function",{"label":29,"jp":960,"en":961},"ストリーム[暗号]{あんごう:cipher}","Stream cipher",{"en":963,"jp":964},"RSA is a representative public-key (asymmetric-key) cipher algorithm using different keys (public and private) for encryption and decryption. AES is the representative symmetric-key cipher.","RSAは[公開鍵]{こうかいかぎ:public key}[暗号]{あんごう:cipher}（[非対称鍵]{ひたいしょうかぎ:asymmetric key}[暗号]{あんごう:cipher}）の[代表的]{だいひょうてき:representative}なアルゴリズム。[暗号化]{あんごうか:encryption}と[復号]{ふくごう:decryption}に[異]{こと:different}なる[鍵]{かぎ:keys}（[公開鍵]{こうかいかぎ:public key}と[秘密鍵]{ひみつかぎ:private key}）を[使用]{しよう:use}する。AESが[共通鍵]{きょうつうかぎ:symmetric key}の[代表]{だいひょう:representative}。",[966],"encryption",{"id":968,"articleId":109,"question":969,"options":972,"correctLabel":25,"explanation":979,"tags":982},"kjh-mock-k2v5-q42",{"en":970,"jp":971},"What type of algorithm is SHA-256?","SHA-256は[何]{なん:what}の[種類]{しゅるい:type}のアルゴリズムか。",[973,974,975,976],{"label":17,"jp":951,"en":952},{"label":21,"jp":954,"en":955},{"label":25,"jp":957,"en":958},{"label":29,"jp":977,"en":978},"[圧縮]{あっしゅく:compression}アルゴリズム","Compression algorithm",{"en":980,"jp":981},"SHA-256 is a hash function in the SHA-2 family that generates a fixed 256-bit hash value from arbitrary-length data. It is used for electronic signatures and data tamper detection.","SHA-256はSHA-2（Secure Hash Algorithm 2）[系列]{けいれつ:family}のハッシュ[関数]{かんすう:function}で、[任意]{にんい:arbitrary}の[長]{なが:length}さのデータから256ビットの[固定]{こてい:fixed}[長]{ちょう:length}ハッシュ[値]{ち:value}を[生成]{せいせい:generate}する。[電子]{でんし:electronic}[署名]{しょめい:signature}やデータの[改]{かい:tamper}ざん[検知]{けんち:detection}に[利用]{りよう:used}される。",[966,983],"hash",{"id":985,"articleId":109,"question":986,"options":989,"correctLabel":17,"explanation":1002,"tags":1005},"kjh-mock-k2v5-q43",{"en":987,"jp":988},"Which correctly describes a characteristic of one-time passwords (OTP)?","ワンタイムパスワード（OTP）の[特徴]{とくちょう:characteristic}として[正]{ただ:correct}しいものはどれか。",[990,993,996,999],{"label":17,"jp":991,"en":992},"[一度]{いちど:once}[使用]{しよう:used}したパスワードは[無効]{むこう:invalidated}になり[再利用]{さいりよう:reuse}できない","A password becomes invalidated after one use and cannot be reused",{"label":21,"jp":994,"en":995},"[同]{おな:same}じパスワードを[何度]{なんど:repeatedly}も[使]{つか:use}える","The same password can be used repeatedly",{"label":25,"jp":997,"en":998},"パスワードの[長]{なが:length}さは[常]{つね:always}に4[桁]{けた:digits}","Password length is always 4 digits",{"label":29,"jp":1000,"en":1001},"[生体]{せいたい:biometric}[認証]{にんしょう:authentication}の[一種]{いっしゅ:type}","A type of biometric authentication",{"en":1003,"jp":1004},"OTP is a disposable password that becomes invalid after one use. Since it cannot be reused even if eavesdropped, it is effective against replay attacks. Classified as \"something you have.\"","ワンタイムパスワードは[一度]{いちど:once}[限]{かぎ:only}りの[使]{つか:disposable}い[捨]{す:disposable}てパスワードで、[使用]{しよう:used}[後]{ご:after}は[無効]{むこう:invalidated}になる。[盗聴]{とうちょう:eavesdropping}されても[再利用]{さいりよう:reuse}できないため、リプレイ[攻撃]{こうげき:attack}への[対策]{たいさく:countermeasure}として[有効]{ゆうこう:effective}。[所持]{しょじ:possession}[情報]{じょうほう:information}（Something you have）に[分類]{ぶんるい:classified}される。",[1006,1007],"authentication","MFA",{"id":1009,"articleId":109,"question":1010,"options":1013,"correctLabel":17,"explanation":1026,"tags":1029},"kjh-mock-k2v5-q44",{"en":1011,"jp":1012},"Which correctly describes an advantage of biometric authentication?","[生体]{せいたい:biometric}[認証]{にんしょう:authentication}の[利点]{りてん:advantage}として[正]{ただ:correct}しいものはどれか。",[1014,1017,1020,1023],{"label":17,"jp":1015,"en":1016},"[紛失]{ふんしつ:loss}や[忘]{わす:forget}れのリスクがない","No risk of loss or forgetting",{"label":21,"jp":1018,"en":1019},"コストが[最]{もっと:most}も[安]{やす:cheap}い","The cheapest option",{"label":25,"jp":1021,"en":1022},"100%の[精度]{せいど:accuracy}で[認証]{にんしょう:authenticate}できる","Can authenticate with 100% accuracy",{"label":29,"jp":1024,"en":1025},"[他人]{たにん:another person}に[貸]{か:lend}すことが[容易]{ようい:easy}","Easy to lend to another person",{"en":1027,"jp":1028},"Biometric authentication uses physical characteristics, so there is no risk of forgetting (like passwords) or losing (like IC cards). However, accuracy is not 100% (FAR\u002FFRR exist), and lending to others is fundamentally impossible.","[生体]{せいたい:biometric}[認証]{にんしょう:authentication}は[身体]{しんたい:body}[的]{てき:-ic}[特徴]{とくちょう:characteristics}を[利用]{りよう:use}するため、パスワードのように[忘]{わす:forget}れたりICカードのように[紛失]{ふんしつ:lose}したりするリスクがない。ただし100%の[精度]{せいど:accuracy}ではなく（FAR・FRRが[存在]{そんざい:exist}）、[他人]{たにん:others}への[貸与]{たいよ:lending}は[原理的]{げんりてき:fundamentally}に[不可能]{ふかのう:impossible}。",[1030,1031],"biometric-authentication","FAR-FRR",{"id":1033,"articleId":109,"question":1034,"options":1037,"correctLabel":17,"explanation":1050,"tags":1053},"kjh-mock-k2v5-q45",{"en":1035,"jp":1036},"Which correctly describes the \"principle of least privilege\" in access control?","アクセス[制御]{せいぎょ:control}の「[最小]{さいしょう:least}[権限]{けんげん:privilege}の[原則]{げんそく:principle}」の[説明]{せつめい:description}として[正]{ただ:correct}しいものはどれか。",[1038,1041,1044,1047],{"label":17,"jp":1039,"en":1040},"[業務]{ぎょうむ:work}に[必要]{ひつよう:necessary}な[最小限]{さいしょうげん:minimum}の[権限]{けんげん:privileges}のみを[付与]{ふよ:grant}する","Granting only the minimum privileges necessary for work",{"label":21,"jp":1042,"en":1043},"[全]{すべ:all}ての[利用者]{りようしゃ:users}にすべての[権限]{けんげん:privileges}を[付与]{ふよ:grant}する","Granting all privileges to all users",{"label":25,"jp":1045,"en":1046},"[管理者]{かんりしゃ:administrators}のみにアクセス[権]{けん:rights}を[付与]{ふよ:grant}する","Granting access rights only to administrators",{"label":29,"jp":1048,"en":1049},"[権限]{けんげん:privileges}の[管理]{かんり:management}は[不要]{ふよう:unnecessary}","Privilege management is unnecessary",{"en":1051,"jp":1052},"The principle of least privilege minimizes damage from unauthorized access or accidental operations by granting users only the minimum privileges necessary for their work.","「[最小]{さいしょう:least}[権限]{けんげん:privilege}の[原則]{げんそく:principle}」は、[利用者]{りようしゃ:users}に[業務]{ぎょうむ:work}の[遂行]{すいこう:performance}に[必要]{ひつよう:necessary}な[最小限]{さいしょうげん:minimum}の[権限]{けんげん:privileges}のみを[付与]{ふよ:grant}することで、[不正]{ふせい:unauthorized}アクセスや[誤操作]{ごそうさ:accidental operation}による[被害]{ひがい:damage}を[最小化]{さいしょうか:minimize}する[原則]{げんそく:principle}。",[1054],"access-control",{"id":1056,"articleId":109,"question":1057,"options":1060,"correctLabel":17,"explanation":1073,"tags":1076},"kjh-mock-k2v5-q46",{"en":1058,"jp":1059},"Which correctly describes the difference between a firewall and a WAF?","ファイアウォールとWAFの[違]{ちが:difference}いとして[正]{ただ:correct}しいものはどれか。",[1061,1064,1067,1070],{"label":17,"jp":1062,"en":1063},"ファイアウォールはネットワーク[層]{そう:layer}、WAFはアプリケーション[層]{そう:layer}で[防御]{ぼうぎょ:defend}する","Firewall defends at the network layer; WAF defends at the application layer",{"label":21,"jp":1065,"en":1066},"[両者]{りょうしゃ:both}は[同]{おな:same}じ[機能]{きのう:function}","Both have the same function",{"label":25,"jp":1068,"en":1069},"WAFはファイアウォールの[旧]{きゅう:old}[名称]{めいしょう:name}","WAF is the old name for firewall",{"label":29,"jp":1071,"en":1072},"ファイアウォールはアプリケーション[層]{そう:layer}、WAFはネットワーク[層]{そう:layer}","Firewall defends at the application layer; WAF at the network layer",{"en":1074,"jp":1075},"Firewalls mainly perform packet filtering at the network layer (IP addresses, port numbers), while WAFs inspect application layer HTTP traffic content to defend against SQL injection, XSS, etc.","ファイアウォールは[主]{おも:mainly}にネットワーク[層]{そう:layer}（IPアドレス、ポート[番号]{ばんごう:numbers}）でパケットフィルタリングを[行]{おこな:conduct}い、WAFはアプリケーション[層]{そう:layer}（HTTP[通信]{つうしん:traffic}の[内容]{ないよう:content}）を[検査]{けんさ:inspect}してSQLインジェクションやXSSなどを[防御]{ぼうぎょ:defend}する。",[1077,1078,1079],"network","WAF","firewall",{"id":1081,"articleId":109,"question":1082,"options":1085,"correctLabel":17,"explanation":1098,"tags":1101},"kjh-mock-k2v5-q47",{"en":1083,"jp":1084},"What is the purpose of VPN tunneling technology?","VPNのトンネリング[技術]{ぎじゅつ:technology}の[目的]{もくてき:purpose}はどれか。",[1086,1089,1092,1095],{"label":17,"jp":1087,"en":1088},"インターネット[上]{じょう:on}に[仮想的]{かそうてき:virtual}な[専用]{せんよう:private}[通信]{つうしん:communication}[路]{ろ:path}を[構築]{こうちく:construct}する","Constructing a virtual private communication path on the internet",{"label":21,"jp":1090,"en":1091},"Webページの[読]{よ:reading}み[込]{こ:loading}み[速度]{そくど:speed}を[向上]{こうじょう:improve}させる","Improving web page loading speed",{"label":25,"jp":1093,"en":1094},"メールの[送受信]{そうじゅしん:sending\u002Freceiving}を[高速化]{こうそくか:speed up}する","Speeding up email sending\u002Freceiving",{"label":29,"jp":1096,"en":1097},"ファイルの[圧縮]{あっしゅく:compression}[率]{りつ:rate}を[上]{あ:raise}げる","Raising file compression rate",{"en":1099,"jp":1100},"VPN tunneling constructs an encrypted virtual private communication path (tunnel) on public networks like the internet, protecting communications from eavesdropping and tampering.","VPNのトンネリングは、インターネットなど[公衆]{こうしゅう:public}ネットワーク[上]{じょう:on}に、[暗号化]{あんごうか:encryption}された[仮想的]{かそうてき:virtual}な[専用]{せんよう:private}[通信]{つうしん:communication}[路]{ろ:path}（トンネル）を[構築]{こうちく:construct}する[技術]{ぎじゅつ:technology}。[盗聴]{とうちょう:eavesdropping}や[改]{かい:tamper}ざんから[通信]{つうしん:communications}を[保護]{ほご:protect}する。",[1102,1077],"VPN",{"id":1104,"articleId":785,"question":1105,"options":1108,"correctLabel":17,"explanation":1121,"tags":1124},"kjh-mock-k2v5-q48",{"en":1106,"jp":1107},"Why is information system monitoring included in technical safety management measures?","[情報]{じょうほう:information}システムの[監視]{かんし:monitoring}が[技術的]{ぎじゅつてき:technical}[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}に[含]{ふく:included}まれる[理由]{りゆう:reason}はどれか。",[1109,1112,1115,1118],{"label":17,"jp":1110,"en":1111},"[不正]{ふせい:unauthorized}アクセスや[異常]{いじょう:anomalous}な[操作]{そうさ:operations}を[早期]{そうき:early}に[発見]{はっけん:discover}するため","To discover unauthorized access and anomalous operations early",{"label":21,"jp":1113,"en":1114},"[従業者]{じゅうぎょうしゃ:employees}の[勤怠]{きんたい:attendance}を[管理]{かんり:manage}するため","To manage employee attendance",{"label":25,"jp":1116,"en":1117},"サーバの[電気]{でんき:electricity}[代]{だい:cost}を[削減]{さくげん:reduce}するため","To reduce server electricity costs",{"label":29,"jp":1119,"en":1120},"オフィスの[温度]{おんど:temperature}を[監視]{かんし:monitor}するため","To monitor office temperature",{"en":1122,"jp":1123},"System monitoring is included in technical measures to discover and respond to unauthorized access and anomalous operations early. Log acquisition and analysis are part of monitoring.","[情報]{じょうほう:information}システムの[監視]{かんし:monitoring}は、[不正]{ふせい:unauthorized}アクセスや[異常]{いじょう:anomalous}な[操作]{そうさ:operations}を[早期]{そうき:early}に[発見]{はっけん:discover}・[対応]{たいおう:respond}するために[技術的]{ぎじゅつてき:technical}[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}に[含]{ふく:included}まれる。ログの[取得]{しゅとく:acquisition}・[分析]{ぶんせき:analysis}も[監視]{かんし:monitoring}の[一環]{いっかん:part}。",[1125,1126],"technical-measures","log-management",{"id":1128,"articleId":785,"question":1129,"options":1132,"correctLabel":17,"explanation":1143,"tags":1146},"kjh-mock-k2v5-q49",{"en":1130,"jp":1131},"Which correctly describes the difference between EDR and conventional antivirus software?","EDRと[従来]{じゅうらい:conventional}のウイルス[対策]{たいさく:countermeasure}ソフトの[違]{ちが:difference}いとして[正]{ただ:correct}しいものはどれか。",[1133,1136,1137,1140],{"label":17,"jp":1134,"en":1135},"ウイルス[対策]{たいさく:countermeasure}ソフトは[侵入]{しんにゅう:intrusion}[前]{まえ:before}の[防止]{ぼうし:prevention}を[重視]{じゅうし:emphasize}、EDRは[侵入]{しんにゅう:intrusion}[後]{ご:after}の[検知]{けんち:detection}・[対応]{たいおう:response}を[重視]{じゅうし:emphasize}","Antivirus emphasizes pre-intrusion prevention; EDR emphasizes post-intrusion detection\u002Fresponse",{"label":21,"jp":1065,"en":1066},{"label":25,"jp":1138,"en":1139},"EDRはネットワーク[機器]{きき:device}、ウイルス[対策]{たいさく:countermeasure}ソフトはPC[用]{よう:for}","EDR is for network devices; antivirus is for PCs",{"label":29,"jp":1141,"en":1142},"EDRは[物理的]{ぶつりてき:physical}セキュリティ、ウイルス[対策]{たいさく:countermeasure}ソフトは[論理的]{ろんりてき:logical}セキュリティ","EDR is physical security; antivirus is logical security",{"en":1144,"jp":1145},"Conventional antivirus emphasizes intrusion prevention based on known malware signatures. EDR assumes intrusion will occur, monitoring endpoint behavior for post-intrusion detection, containment, and investigation.","[従来]{じゅうらい:conventional}のウイルス[対策]{たいさく:countermeasure}ソフトは[既知]{きち:known}のマルウェアのシグネチャに[基]{もと:based}づく[侵入]{しんにゅう:intrusion}[防止]{ぼうし:prevention}を[重視]{じゅうし:emphasize}。EDRは[侵入]{しんにゅう:intrusion}を[前提]{ぜんてい:assume}とし、エンドポイントの[挙動]{きょどう:behavior}を[監視]{かんし:monitor}して[侵入]{しんにゅう:intrusion}[後]{ご:after}の[検知]{けんち:detection}・[封]{ふう:contain}じ[込]{こ:contain}め・[調査]{ちょうさ:investigation}を[行]{おこな:conduct}う。",[1147,59],"EDR",{"id":1149,"articleId":1150,"question":1151,"options":1154,"correctLabel":17,"explanation":1167,"tags":1170},"kjh-mock-k2v5-q50","kjh-k1-h04-gaikoku-kiroku",{"en":1152,"jp":1153},"What is the correct reason for verifying data location when using cloud services?","クラウドサービス[利用]{りよう:use}[時]{じ:time}にデータの[所在地]{しょざいち:location}を[確認]{かくにん:verify}する[理由]{りゆう:reason}として[正]{ただ:correct}しいものはどれか。",[1155,1158,1161,1164],{"label":17,"jp":1156,"en":1157},"データの[保存先]{ほぞんさき:storage location}の[国]{くに:country}の[法律]{ほうりつ:laws}が[適用]{てきよう:applied}される[可能性]{かのうせい:possibility}があり、[個人情報]{こじんじょうほう:personal information}[保護]{ほご:protection}の[水準]{すいじゅん:level}が[異]{こと:differ}なるため","Laws of the country where data is stored may apply, and personal information protection levels differ",{"label":21,"jp":1159,"en":1160},"[通信]{つうしん:communication}[速度]{そくど:speed}を[最適化]{さいてきか:optimize}するため","To optimize communication speed",{"label":25,"jp":1162,"en":1163},"データの[所在地]{しょざいち:location}はセキュリティに[影響]{えいきょう:impact}しない","Data location does not impact security",{"label":29,"jp":1165,"en":1166},"[料金]{りょうきん:fees}を[安]{やす:cheap}くするため","To reduce fees",{"en":1168,"jp":1169},"In cloud services, laws of the data storage country may apply. Since PI protection levels differ by country, special attention is needed when data is stored abroad.","クラウドサービスでは、データの[保存先]{ほぞんさき:storage location}の[国]{くに:country}の[法律]{ほうりつ:laws}が[適用]{てきよう:applied}される[可能性]{かのうせい:possibility}がある。[個人情報]{こじんじょうほう:personal information}[保護]{ほご:protection}の[水準]{すいじゅん:level}は[国]{くに:country}により[異]{こと:differ}なるため、[外国]{がいこく:foreign}にデータが[保存]{ほぞん:stored}される[場合]{ばあい:case}は[特]{とく:especially}に[注意]{ちゅうい:attention}が[必要]{ひつよう:necessary}。",[1171,1172],"cloud","shared-responsibility",{"culture-anime-studio-ghibli":1174,"culture-bonsai-art":1178,"tech-cybozu-kintone-no-code":1182,"living-denki-gas-suidou":1186,"tech-gree-mobile-game-ops":1190,"culture-green-tea-types":1194,"living-gym-fitness":1198,"living-internet-hikari":1202,"living-jisha-de-kau":1206,"exam-jlpt-n3-grammar":1210,"exam-jlpt-n3-vocab":1214,"bj-job-gata-koyou":1218,"culture-kabuki-noh-bunraku":1222,"bj-karoushi-hatarakikata":1226,"living-keitai-mobile-plan":1230,"living-konbini-atm-banking":1234,"living-kosodate-hoiku":1238,"culture-nihon-teien":1242,"bj-nomikai-survival":1246,"tech-pixiv-image-cdn":1250,"culture-sake-shochu":1254,"bj-sankyu-ikukyu":1258,"tech-sansan-eight-platform":1262,"culture-shichi-go-san":1266,"bj-shukatsu-shinsotsu":1270,"tech-smartnews-recommendation":1274,"bj-taishoku-todoke":1278,"bj-telework-policy":1282,"bj-tenshoku-resume":1286,"tech-yahoo-japan-search":1290,"culture-anime-business":1294,"exam-ap":1298,"exam-aws-japan":1302,"law-chosakuken":1306,"tech-cookpad-recipe-search":1310,"tech-cybozu-kintone-api":1314,"tech-dena-observability":1318,"law-denshi-chouho":1322,"tech-digital-cho-cloud":1326,"exam-fe":1330,"tech-freee-accounting":1334,"law-furiransu-hou":1338,"law-harassment":1342,"tech-hatena-mackerel":1346,"bj-hourensou":1350,"bj-hyouka-mendan":1354,"law-invoice":1358,"exam-it-passport":1362,"culture-izakaya":1366,"culture-j-league":1370,"culture-jinja-tera":1374,"exam-jlpt-n1-dokkai":1378,"exam-jlpt-n2-business":1382,"bj-kaigi-manner":1386,"living-kakutei-shinkoku":1390,"bj-keigo-kihon":1394,"law-keihin-hyouji":1398,"living-kenkou-hoken":1402,"living-kosei-nenkin":1406,"tech-line-llmops":1410,"tech-line-streaming":1414,"living-chintai-keiyaku":1418,"living-eijuken":1422,"living-engineer-visa":1426,"living-ginkou-koza":1430,"living-hikkoshi-checklist":1434,"living-koudo-senmon":1438,"culture-matsuri":1442,"bj-meishi-koukan":1446,"tech-mercari-merpay-id":1450,"tech-mercari-microservices":1454,"tech-mf-multitenant":1458,"bj-nemawashi-ringi":1462,"living-nenmatsu-chousei":1466,"bj-1on1":1470,"bj-online-kaigi":1474,"culture-onsen":1478,"culture-pro-baseball":1482,"culture-ramen":1486,"tech-recruit-data-platform":1490,"law-roukikihou-kihon":1494,"culture-sado":1498,"culture-sandou":1502,"culture-seasonal-events":1506,"exam-sg":1510,"bj-shagai-mail":1514,"bj-shanai-mail":1518,"culture-sumo":1522,"culture-sushi":1526,"culture-washoku":1530,"law-yuukyuu-kyuuka":1534,"kjh-k1-h04-anzen-kanri":1538,"bill-one-auth":1541,"contract-one-vision":1545,"kjh-k1-h04-daisan-sha-teikyou":1549,"eight-web-renewal":1552,"kjh-k1-h04-gaikoku-kiroku":1556,"kjh-k2-h04-gijutsu-jisshi":1559,"kjh-k2-h04-gijutsu-kiso":1562,"kjh-k1-h01-hotaikei":1565,"kjh-k1-h06-hoyu-data":1568,"kjh-k1-h07-kamei-kakou":1572,"kjh-k1-h05-kanren-joho":1576,"kjh-k1-h02-kihon-rinen":1580,"kjh-k1-h09-jikkousei":1584,"kjh-k1-h10-gyousei":1588,"kjh-k1-h11-my-number-hogo":1592,"kjh-k1-h11-my-number-sousoku":1595,"kjh-k2-h01-guideline":1598,"kjh-k2-h01-security-kiso":1601,"kjh-k2-h02-anzen-kanri-sochi":1604,"kjh-k2-h02-soshiki-kiso":1607,"kjh-k2-h03-office":1610,"kjh-k1-h03-riyou-mokuteki":1613,"sansan-data-intelligence":1617,"sansan-engineer-team-infra":1621,"sansan-honne-15":1625,"sansan-interview-110":1629,"sansan-interview-126":1633,"sansan-interview-127":1637,"sansan-interview-130":1641,"sansan-interview-40":1645,"sansan-oyaco":1649,"kjh-k1-h03-tekisei-shutoku":1653,"kjh-k1-h08-tokumei-kakou":1657},{"articleId":1175,"path":1176,"title":1177},"culture-anime-studio-ghibli","\u002Farticles\u002Fculture\u002Fanime-studio-ghibli","スタジオジブリ作品史 — 宮崎駿・高畑勲・鈴木敏夫が築いた40年",{"articleId":1179,"path":1180,"title":1181},"culture-bonsai-art","\u002Farticles\u002Fculture\u002Fbonsai-art","盆栽の世界 — 小宇宙を育てる日本の芸術",{"articleId":1183,"path":1184,"title":1185},"tech-cybozu-kintone-no-code","\u002Farticles\u002Ftech\u002Fcybozu-kintone-no-code","kintoneのローコード戦略 — 業務アプリを誰でも作れる仕組み",{"articleId":1187,"path":1188,"title":1189},"living-denki-gas-suidou","\u002Farticles\u002Fliving-in-japan\u002Fdenki-gas-suidou","電気・ガス・水道の契約 — 引越し時のライフライン手続き",{"articleId":1191,"path":1192,"title":1193},"tech-gree-mobile-game-ops","\u002Farticles\u002Ftech\u002Fgree-mobile-game-ops","GREEのモバイルゲーム運用 — リアルタイム対戦と決済の裏側",{"articleId":1195,"path":1196,"title":1197},"culture-green-tea-types","\u002Farticles\u002Fculture\u002Fgreen-tea-types","日本茶の種類と淹れ方 — 煎茶・玉露・抹茶の違い",{"articleId":1199,"path":1200,"title":1201},"living-gym-fitness","\u002Farticles\u002Fliving-in-japan\u002Fgym-fitness","ジムとフィットネスクラブ — 入会から解約までの実務ガイド",{"articleId":1203,"path":1204,"title":1205},"living-internet-hikari","\u002Farticles\u002Fliving-in-japan\u002Finternet-hikari-keiyaku","光回線とネット契約 — フレッツ・NURO・auひかり比較",{"articleId":1207,"path":1208,"title":1209},"living-jisha-de-kau","\u002Farticles\u002Fliving-in-japan\u002Fjisha-de-kau","日本で不動産を買う — 外国人でも住宅ローンを組む方法",{"articleId":1211,"path":1212,"title":1213},"exam-jlpt-n3-grammar","\u002Farticles\u002Fexams\u002Fjlpt-n3-grammar","JLPT N3 文法 — 初級から中級への橋渡し",{"articleId":1215,"path":1216,"title":1217},"exam-jlpt-n3-vocab","\u002Farticles\u002Fexams\u002Fjlpt-n3-vocab","JLPT N3 語彙対策 — 1500語をどう攻略するか",{"articleId":1219,"path":1220,"title":1221},"bj-job-gata-koyou","\u002Farticles\u002Fbusiness-japanese\u002Fjob-gata-koyou","ジョブ型雇用への移行 — メンバーシップ型からの脱却",{"articleId":1223,"path":1224,"title":1225},"culture-kabuki-noh-bunraku","\u002Farticles\u002Fculture\u002Fkabuki-noh-bunraku","歌舞伎・能・文楽 — 日本三大伝統演劇の世界",{"articleId":1227,"path":1228,"title":1229},"bj-karoushi-hatarakikata","\u002Farticles\u002Fbusiness-japanese\u002Fkaroushi-hatarakikata","過労死と働き方改革 — 残業規制の歴史と現状",{"articleId":1231,"path":1232,"title":1233},"living-keitai-mobile-plan","\u002Farticles\u002Fliving-in-japan\u002Fkeitai-mobile-plan","携帯電話契約の選び方 — 大手キャリア・MVNO・eSIM完全ガイド",{"articleId":1235,"path":1236,"title":1237},"living-konbini-atm-banking","\u002Farticles\u002Fliving-in-japan\u002Fkonbini-atm-banking","コンビニATMと電子マネー — 現金とキャッシュレスのハイブリッド生活",{"articleId":1239,"path":1240,"title":1241},"living-kosodate-hoiku","\u002Farticles\u002Fliving-in-japan\u002Fkosodate-hoiku","子育て支援と保育園 — 児童手当・保活・無償化制度",{"articleId":1243,"path":1244,"title":1245},"culture-nihon-teien","\u002Farticles\u002Fculture\u002Fnihon-teien","日本庭園の世界 — 池泉・枯山水・露地の様式",{"articleId":1247,"path":1248,"title":1249},"bj-nomikai-survival","\u002Farticles\u002Fbusiness-japanese\u002Fnomikai-survival","飲み会・ノミニケーション完全攻略 — 新人エンジニアのサバイバルガイド",{"articleId":1251,"path":1252,"title":1253},"tech-pixiv-image-cdn","\u002Farticles\u002Ftech\u002Fpixiv-image-cdn","pixivの画像配信基盤 — 数億イラストを世界に届ける技術",{"articleId":1255,"path":1256,"title":1257},"culture-sake-shochu","\u002Farticles\u002Fculture\u002Fsake-shochu","日本酒と焼酎入門 — 製法・産地・飲み方の基礎",{"articleId":1259,"path":1260,"title":1261},"bj-sankyu-ikukyu","\u002Farticles\u002Fbusiness-japanese\u002Fsankyu-ikukyu","産休・育休制度の実務 — 取得スケジュールと給付金",{"articleId":1263,"path":1264,"title":1265},"tech-sansan-eight-platform","\u002Farticles\u002Ftech\u002Fsansan-eight-platform","Eight 名刺SaaSの基盤進化 — モバイルから法人向けプラットフォームへ",{"articleId":1267,"path":1268,"title":1269},"culture-shichi-go-san","\u002Farticles\u002Fculture\u002Fshichi-go-san","七五三 — 子供の成長を祝う伝統行事",{"articleId":1271,"path":1272,"title":1273},"bj-shukatsu-shinsotsu","\u002Farticles\u002Fbusiness-japanese\u002Fshukatsu-shinsotsu","新卒就活の流れ — エントリーシートから内定まで",{"articleId":1275,"path":1276,"title":1277},"tech-smartnews-recommendation","\u002Farticles\u002Ftech\u002Fsmartnews-recommendation","SmartNewsの推薦システム — ニュースを最適化する機械学習",{"articleId":1279,"path":1280,"title":1281},"bj-taishoku-todoke","\u002Farticles\u002Fbusiness-japanese\u002Ftaishoku-todoke","退職届と退職願 — 違いと書き方、円満退職への手順",{"articleId":1283,"path":1284,"title":1285},"bj-telework-policy","\u002Farticles\u002Fbusiness-japanese\u002Ftelework-policy","テレワーク制度の現状 — コロナ後の在宅勤務とハイブリッド",{"articleId":1287,"path":1288,"title":1289},"bj-tenshoku-resume","\u002Farticles\u002Fbusiness-japanese\u002Ftenshoku-resume","転職活動の進め方 — 履歴書と職務経歴書の書き方",{"articleId":1291,"path":1292,"title":1293},"tech-yahoo-japan-search","\u002Farticles\u002Ftech\u002Fyahoo-japan-search","Yahoo! JAPAN検索の基盤 — 日本語特化の大規模検索システム",{"articleId":1295,"path":1296,"title":1297},"culture-anime-business","\u002Farticles\u002Fculture\u002Fanime-business","アニメ・漫画文化と産業構造 — グローバル展開の現状",{"articleId":1299,"path":1300,"title":1301},"exam-ap","\u002Farticles\u002Fexams\u002Fap","応用情報技術者試験 — 重点出題分野",{"articleId":1303,"path":1304,"title":1305},"exam-aws-japan","\u002Farticles\u002Fexams\u002Faws-japan","AWS認定 — 日本語受験のコツ",{"articleId":1307,"path":1308,"title":1309},"law-chosakuken","\u002Farticles\u002Flaw\u002Fchosakuken","著作権法 — エンジニアが知っておくべき基礎",{"articleId":1311,"path":1312,"title":1313},"tech-cookpad-recipe-search","\u002Farticles\u002Ftech\u002Fcookpad-recipe-search-ranking","Cookpadのレシピ検索 — 学習to-rank実装",{"articleId":1315,"path":1316,"title":1317},"tech-cybozu-kintone-api","\u002Farticles\u002Ftech\u002Fcybozu-kintone-api-design","kintone API設計の十年 — 後方互換性との戦い",{"articleId":1319,"path":1320,"title":1321},"tech-dena-observability","\u002Farticles\u002Ftech\u002Fdena-mobile-game-observability","DeNAのモバイルゲーム監視基盤",{"articleId":1323,"path":1324,"title":1325},"law-denshi-chouho","\u002Farticles\u002Flaw\u002Fdenshi-chouho","電子帳簿保存法 — スキャナ保存と電子取引保存の対応",{"articleId":1327,"path":1328,"title":1329},"tech-digital-cho-cloud","\u002Farticles\u002Ftech\u002Fdigital-cho-government-cloud","デジタル庁ガバメントクラウド技術詳細",{"articleId":1331,"path":1332,"title":1333},"exam-fe","\u002Farticles\u002Fexams\u002Ffe","基本情報技術者試験 — シラバス全体像",{"articleId":1335,"path":1336,"title":1337},"tech-freee-accounting","\u002Farticles\u002Ftech\u002Ffreee-accounting-integrity","freeeの会計データ整合性 — 仕訳バランスの自動検証",{"articleId":1339,"path":1340,"title":1341},"law-furiransu-hou","\u002Farticles\u002Flaw\u002Ffuriransu-hou","フリーランス保護法（2024年施行）— 取引適正化のポイント",{"articleId":1343,"path":1344,"title":1345},"law-harassment","\u002Farticles\u002Flaw\u002Fharassment","ハラスメント関連法 — パワハラ・セクハラ・マタハラ防止義務",{"articleId":1347,"path":1348,"title":1349},"tech-hatena-mackerel","\u002Farticles\u002Ftech\u002Fhatena-mackerel-alert-design","MackerelのAlert設計思想",{"articleId":1351,"path":1352,"title":1353},"bj-hourensou","\u002Farticles\u002Fbusiness-japanese\u002Fhourensou","報・連・相 — 日本企業のコミュニケーションの基本",{"articleId":1355,"path":1356,"title":1357},"bj-hyouka-mendan","\u002Farticles\u002Fbusiness-japanese\u002Fhyouka-mendan","評価面談の準備と振り返り",{"articleId":1359,"path":1360,"title":1361},"law-invoice","\u002Farticles\u002Flaw\u002Finvoice-seido","インボイス制度の仕組みと実務 — 適格請求書発行事業者",{"articleId":1363,"path":1364,"title":1365},"exam-it-passport","\u002Farticles\u002Fexams\u002Fit-passport","ITパスポート試験 — 概要と学習法",{"articleId":1367,"path":1368,"title":1369},"culture-izakaya","\u002Farticles\u002Fculture\u002Fizakaya","居酒屋文化と乾杯のマナー — お通しから締めまで",{"articleId":1371,"path":1372,"title":1373},"culture-j-league","\u002Farticles\u002Fculture\u002Fj-league","Jリーグの歴史と地域密着 — 1993年開幕から30年",{"articleId":1375,"path":1376,"title":1377},"culture-jinja-tera","\u002Farticles\u002Fculture\u002Fjinja-tera","神社と寺の違い、参拝マナー",{"articleId":1379,"path":1380,"title":1381},"exam-jlpt-n1-dokkai","\u002Farticles\u002Fexams\u002Fjlpt-n1-dokkai","JLPT N1 — 読解問題のアプローチ",{"articleId":1383,"path":1384,"title":1385},"exam-jlpt-n2-business","\u002Farticles\u002Fexams\u002Fjlpt-n2-business","JLPT N2 — ビジネス語彙集中対策",{"articleId":1387,"path":1388,"title":1389},"bj-kaigi-manner","\u002Farticles\u002Fbusiness-japanese\u002Fkaigi-manner","会議のマナーと進め方 — 司会から議事録まで",{"articleId":1391,"path":1392,"title":1393},"living-kakutei-shinkoku","\u002Farticles\u002Fliving-in-japan\u002Fkakutei-shinkoku","確定申告の基本 — 給与所得・副業・控除",{"articleId":1395,"path":1396,"title":1397},"bj-keigo-kihon","\u002Farticles\u002Fbusiness-japanese\u002Fkeigo-kihon","ビジネス敬語の基本 — 尊敬語・謙譲語・丁寧語の使い分け",{"articleId":1399,"path":1400,"title":1401},"law-keihin-hyouji","\u002Farticles\u002Flaw\u002Fkeihin-hyouji","改正景品表示法とステマ規制 — マーケティングの法的注意点",{"articleId":1403,"path":1404,"title":1405},"living-kenkou-hoken","\u002Farticles\u002Fliving-in-japan\u002Fkenkou-hoken","健康保険の入門 — 国保と社保の違い",{"articleId":1407,"path":1408,"title":1409},"living-kosei-nenkin","\u002Farticles\u002Fliving-in-japan\u002Fkosei-nenkin","厚生年金と国民年金 — 老後の備えと現役の負担",{"articleId":1411,"path":1412,"title":1413},"tech-line-llmops","\u002Farticles\u002Ftech\u002Fline-llmops","LINEのLLMOps — 大規模言語モデル運用の取り組み",{"articleId":1415,"path":1416,"title":1417},"tech-line-streaming","\u002Farticles\u002Ftech\u002Fline-streaming","LINEの大規模リアルタイム配信基盤",{"articleId":1419,"path":1420,"title":1421},"living-chintai-keiyaku","\u002Farticles\u002Fliving-in-japan\u002Fliving-chintai-keiyaku","賃貸契約と保証会社 — 礼金・敷金から保証料まで",{"articleId":1423,"path":1424,"title":1425},"living-eijuken","\u002Farticles\u002Fliving-in-japan\u002Fliving-eijuken","永住権申請の最新基準 — 一般・高度専門職ルート比較",{"articleId":1427,"path":1428,"title":1429},"living-engineer-visa","\u002Farticles\u002Fliving-in-japan\u002Fliving-engineer-visa","エンジニアの在留資格 — 「技術・人文知識・国際業務」ビザの取得手順",{"articleId":1431,"path":1432,"title":1433},"living-ginkou-koza","\u002Farticles\u002Fliving-in-japan\u002Fliving-ginkou-koza","銀行口座開設とクレジットカード — 外国人エンジニアの実務",{"articleId":1435,"path":1436,"title":1437},"living-hikkoshi-checklist","\u002Farticles\u002Fliving-in-japan\u002Fliving-hikkoshi-checklist","引越し手続きチェックリスト — 役所・ライフライン・住所変更",{"articleId":1439,"path":1440,"title":1441},"living-koudo-senmon","\u002Farticles\u002Fliving-in-japan\u002Fliving-koudo-senmon","高度専門職ビザの実務 — ポイント制度と特権",{"articleId":1443,"path":1444,"title":1445},"culture-matsuri","\u002Farticles\u002Fculture\u002Fmatsuri","日本の祭り — 季節と地域の象徴",{"articleId":1447,"path":1448,"title":1449},"bj-meishi-koukan","\u002Farticles\u002Fbusiness-japanese\u002Fmeishi-koukan","名刺交換の作法 — 第一印象を決める数十秒",{"articleId":1451,"path":1452,"title":1453},"tech-mercari-merpay-id","\u002Farticles\u002Ftech\u002Fmercari-merpay-id","メルペイのID基盤 — eKYC・本人確認の技術",{"articleId":1455,"path":1456,"title":1457},"tech-mercari-microservices","\u002Farticles\u002Ftech\u002Fmercari-microservices-migration","Mercariのマイクロサービス移行 — モノリスから次世代へ",{"articleId":1459,"path":1460,"title":1461},"tech-mf-multitenant","\u002Farticles\u002Ftech\u002Fmoneyforward-multitenant-saas","Money Forwardのマルチテナント設計 — データ分離とセキュリティ",{"articleId":1463,"path":1464,"title":1465},"bj-nemawashi-ringi","\u002Farticles\u002Fbusiness-japanese\u002Fnemawashi-ringi","根回しと稟議 — 日本企業の意思決定の仕組み",{"articleId":1467,"path":1468,"title":1469},"living-nenmatsu-chousei","\u002Farticles\u002Fliving-in-japan\u002Fnenmatsu-chousei","年末調整の仕組み — 会社員のための税精算",{"articleId":1471,"path":1472,"title":1473},"bj-1on1","\u002Farticles\u002Fbusiness-japanese\u002Fone-on-one","1on1ミーティングの活用法 — 上司と部下の対話",{"articleId":1475,"path":1476,"title":1477},"bj-online-kaigi","\u002Farticles\u002Fbusiness-japanese\u002Fonline-kaigi","オンライン会議のエチケット — Zoom時代のビジネスマナー",{"articleId":1479,"path":1480,"title":1481},"culture-onsen","\u002Farticles\u002Fculture\u002Fonsen","温泉文化と入浴マナー — 名湯巡りの楽しみ方",{"articleId":1483,"path":1484,"title":1485},"culture-pro-baseball","\u002Farticles\u002Fculture\u002Fpro-baseball","プロ野球と高校野球 — 国民的スポーツの二つの顔",{"articleId":1487,"path":1488,"title":1489},"culture-ramen","\u002Farticles\u002Fculture\u002Framen","ラーメン地域ごとの違い — 札幌・博多・喜多方",{"articleId":1491,"path":1492,"title":1493},"tech-recruit-data-platform","\u002Farticles\u002Ftech\u002Frecruit-data-platform","Recruit データ基盤刷新事例 — 数十サービスの統合",{"articleId":1495,"path":1496,"title":1497},"law-roukikihou-kihon","\u002Farticles\u002Flaw\u002Froukikihou-kihon","労働基準法の基本 — 労働時間・休憩・残業規制",{"articleId":1499,"path":1500,"title":1501},"culture-sado","\u002Farticles\u002Fculture\u002Fsado","茶道入門 — 千利休と侘び寂びの精神",{"articleId":1503,"path":1504,"title":1505},"culture-sandou","\u002Farticles\u002Fculture\u002Fsandou","茶華書三道 — 日本の精神を体現する三つの道",{"articleId":1507,"path":1508,"title":1509},"culture-seasonal-events","\u002Farticles\u002Fculture\u002Fseasonal-events","季節の行事 — 正月から年末まで日本の年中行事",{"articleId":1511,"path":1512,"title":1513},"exam-sg","\u002Farticles\u002Fexams\u002Fsg","情報セキュリティマネジメント試験 — 管理者向けセキュリティ",{"articleId":1515,"path":1516,"title":1517},"bj-shagai-mail","\u002Farticles\u002Fbusiness-japanese\u002Fshagai-mail","社外メールの書き方 — お詫び・依頼・確認",{"articleId":1519,"path":1520,"title":1521},"bj-shanai-mail","\u002Farticles\u002Fbusiness-japanese\u002Fshanai-mail","社内メールの書き方 — 件名から結びまで",{"articleId":1523,"path":1524,"title":1525},"culture-sumo","\u002Farticles\u002Fculture\u002Fsumo","大相撲 — 番付と力士の生活",{"articleId":1527,"path":1528,"title":1529},"culture-sushi","\u002Farticles\u002Fculture\u002Fsushi","寿司の歴史と種類 — なれずしから江戸前まで",{"articleId":1531,"path":1532,"title":1533},"culture-washoku","\u002Farticles\u002Fculture\u002Fwashoku","和食 — ユネスコ無形文化遺産と一汁三菜",{"articleId":1535,"path":1536,"title":1537},"law-yuukyuu-kyuuka","\u002Farticles\u002Flaw\u002Fyuukyuu-kyuuka","有給休暇の取得ルールと最新改正",{"articleId":366,"path":1539,"title":1540},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fanzen-kanri","課題Ⅰ 第４編① 個人データに関する義務 ― 正確性の確保・安全管理措置・漏えい報告",{"articleId":1542,"path":1543,"title":1544},"bill-one-auth","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fbill-one-auth","インボイス管理サービスBill Oneの認証を内製認証基盤に置き換えて認証基盤のコストを削減した話",{"articleId":1546,"path":1547,"title":1548},"contract-one-vision","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fcontract-one-vision","契約書を\"意思決定のインフラ\"に──Contract Oneで挑む、新たな価値創造",{"articleId":555,"path":1550,"title":1551},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fdaisan-sha-teikyou","課題Ⅰ 第４編② 第三者提供の制限 ― 同意・オプトアウト・非該当類型",{"articleId":1553,"path":1554,"title":1555},"eight-web-renewal","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Feight-web-renewal","Web版Eightのリニューアルと、安全なリリースのための取り組み",{"articleId":1150,"path":1557,"title":1558},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fgaikoku-kiroku","課題Ⅰ 第４編③ 外国にある第三者への提供の制限・記録義務・確認義務（法28条〜30条）",{"articleId":785,"path":1560,"title":1561},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fgijutsu-jisshi","課題Ⅱ 第４編② 技術的安全管理措置の実施項目",{"articleId":109,"path":1563,"title":1564},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fgijutsu-kiso","課題Ⅱ 第４編① 技術的セキュリティ対策の基礎知識",{"articleId":249,"path":1566,"title":1567},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fhotaikei","課題Ⅰ 第１編 個人情報保護の法体系と各種認定制度",{"articleId":1569,"path":1570,"title":1571},"kjh-k1-h06-hoyu-data","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fhoyu-data","課題Ⅰ 第６編 保有個人データに関する義務",{"articleId":1573,"path":1574,"title":1575},"kjh-k1-h07-kamei-kakou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkamei-kakou","課題Ⅰ 第７編 仮名加工情報（法41条・42条）",{"articleId":1577,"path":1578,"title":1579},"kjh-k1-h05-kanren-joho","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkanren-joho","課題Ⅰ 第５編 個人関連情報に関する義務（法31条）",{"articleId":1581,"path":1582,"title":1583},"kjh-k1-h02-kihon-rinen","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkihon-rinen","課題Ⅰ 第２編 個人情報保護法の目的・基本理念と用語の定義",{"articleId":1585,"path":1586,"title":1587},"kjh-k1-h09-jikkousei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h09-jikkousei","課題Ⅰ 第９編 実効性を担保する仕組み等",{"articleId":1589,"path":1590,"title":1591},"kjh-k1-h10-gyousei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h10-gyousei","課題Ⅰ 第10編 行政機関等における個人情報等の取扱い",{"articleId":390,"path":1593,"title":1594},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h11-my-number-hogo","課題Ⅰ 第11編② マイナンバー法 ― 特定個人情報の提供制限・保護・監督・罰則（法19条〜57条）",{"articleId":738,"path":1596,"title":1597},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h11-my-number-sousoku","課題Ⅰ 第11編① マイナンバー法 ― 総則・個人番号・個人番号カード（法1条〜18条の5）",{"articleId":225,"path":1599,"title":1600},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h01-guideline","課題Ⅱ 第１編② セキュリティ対策基準とガイドライン",{"articleId":11,"path":1602,"title":1603},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h01-security-kiso","課題Ⅱ 第１編① 情報セキュリティの基礎と脅威",{"articleId":485,"path":1605,"title":1606},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h02-anzen-kanri-sochi","課題Ⅱ 第２編② 組織的・人的セキュリティ ― 安全管理措置・委託先監督・事故対応",{"articleId":414,"path":1608,"title":1609},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h02-soshiki-kiso","課題Ⅱ 第２編① 組織的・人的セキュリティ ― 基本方針の策定からリスク管理・規程整備まで",{"articleId":714,"path":1611,"title":1612},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Foffice","課題Ⅱ 第３編 オフィスセキュリティ",{"articleId":1614,"path":1615,"title":1616},"kjh-k1-h03-riyou-mokuteki","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Friyou-mokuteki","課題Ⅰ 第３編① 利用目的の特定・変更と利用目的による制限、不適正な利用の禁止",{"articleId":1618,"path":1619,"title":1620},"sansan-data-intelligence","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-data-intelligence","Sansan Data Intelligenceリリースに寄せて",{"articleId":1622,"path":1623,"title":1624},"sansan-engineer-team-infra","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-engineer-team-infra","Sansan Engineer Team：インフラ戦略部",{"articleId":1626,"path":1627,"title":1628},"sansan-honne-15","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-honne-15","入社後のホンネ［技術本部 データ戦略部 Infrastructureグループ 渡邉 友］",{"articleId":1630,"path":1631,"title":1632},"sansan-interview-110","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-110","SIer出身者が活躍する理由とは。Sansanを牽引するプロダクト開発に挑み続ける",{"articleId":1634,"path":1635,"title":1636},"sansan-interview-126","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-126","AIと協働する開発組織、そして技術の深化。Sansan 新CTO笹川が語るビジョン",{"articleId":1638,"path":1639,"title":1640},"sansan-interview-127","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-127","Sansanの技術基盤を関西から築く。新設組織で未来を創る、エンジニアの挑戦",{"articleId":1642,"path":1643,"title":1644},"sansan-interview-130","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-130","Sansanの全社基盤を支えるPlatform Engineering Unitの挑戦",{"articleId":1646,"path":1647,"title":1648},"sansan-interview-40","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-40","膨大な量のデータを平然と処理する。Sansanのインフラのすごさが、そこに表れている。",{"articleId":1650,"path":1651,"title":1652},"sansan-oyaco","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-oyaco","仕事と子育ての両立を支援する制度「OYACO」",{"articleId":1654,"path":1655,"title":1656},"kjh-k1-h03-tekisei-shutoku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Ftekisei-shutoku","課題Ⅰ 第３編② 適正な取得・要配慮個人情報・利用目的の通知",{"articleId":1658,"path":1659,"title":1660},"kjh-k1-h08-tokumei-kakou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Ftokumei-kakou","課題Ⅰ 第８編 匿名加工情報に関する義務等（法43条〜46条）"]