[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"quiz:kjh-k2-h02-quiz":3,"quiz-article-index":323},{"quizId":4,"title":5,"titleEn":6,"topicPath":7,"questions":8},"kjh-k2-h02-quiz","第２編 組織的・人的セキュリティ 確認テスト","Chapter 2: Organizational & Human Security — Practice Test","software\u002Fkojin-joho-hogo\u002Fkadai-2\u002Fhen-02-soshikiteki-jinteki",[9,37,61,85,109,132,156,180,204,228,252,277,300],{"id":10,"articleId":11,"question":12,"options":15,"correctLabel":17,"explanation":32,"tags":35},"kjh-k2-h02-q01","kjh-k2-h02-soshiki-kiso",{"en":13,"jp":14},"Among the four risk treatment methods, what is it called when you stop the activity that causes the risk entirely?","リスク[対策]{たいさく:countermeasure}の4[手法]{しゅほう:methods}のうち、リスクの[原因]{げんいん:cause}となる[活動]{かつどう:activity}[自体]{じたい:itself}を[取]{と:take}りやめることを[何]{なに:what}というか。",[16,20,24,28],{"label":17,"jp":18,"en":19},"ア","リスク[回避]{かいひ:avoidance}","Risk avoidance",{"label":21,"jp":22,"en":23},"イ","リスク[低減]{ていげん:reduction}","Risk reduction",{"label":25,"jp":26,"en":27},"ウ","リスク[移転]{いてん:transfer}","Risk transfer",{"label":29,"jp":30,"en":31},"エ","リスク[受容]{じゅよう:acceptance}","Risk acceptance",{"en":33,"jp":34},"Risk avoidance means discontinuing the activity that causes the risk. Reduction lowers the probability or impact through security measures. Transfer shifts the risk to others via insurance or outsourcing. Acceptance means tolerating the risk as-is.","リスク[回避]{かいひ:avoidance}は、リスクの[原因]{げんいん:cause}となる[活動]{かつどう:activity}そのものを[中止]{ちゅうし:discontinue}する[方法]{ほうほう:method}。[低減]{ていげん:reduction}はセキュリティ[対策]{たいさく:countermeasure}で[発生]{はっせい:occurrence}[確率]{かくりつ:probability}や[影響]{えいきょう:impact}を[下]{さ:lower}げること、[移転]{いてん:transfer}は[保険]{ほけん:insurance}や[外部]{がいぶ:external}[委託]{いたく:outsourcing}でリスクを[他者]{たしゃ:others}に[移]{うつ:transfer}すこと、[受容]{じゅよう:acceptance}はリスクをそのまま[受]{う:accept}け[入]{い:accept}れることである。",[36],"risk-management",{"id":38,"articleId":39,"question":40,"options":43,"correctLabel":25,"explanation":56,"tags":59},"kjh-k2-h02-q02","kjh-k1-h04-anzen-kanri",{"en":41,"jp":42},"Which of the following is NOT included in the organizational safety management measures under the Personal Information Protection Act guidelines?","[個人情報]{こじんじょうほう:personal information}[保護法]{ほごほう:protection law}ガイドラインにおける[組織的]{そしきてき:organizational}[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}に[含]{ふく:include}まれないものはどれか。",[44,47,50,53],{"label":17,"jp":45,"en":46},"[組織]{そしき:organization}[体制]{たいせい:structure}の[整備]{せいび:establishment}","Establishment of organizational structure",{"label":21,"jp":48,"en":49},"[個人]{こじん:personal}データの[取扱]{とりあつかい:handling}いに[係]{かか:related}る[規律]{きりつ:rules}の[整備]{せいび:establishment}","Establishment of rules for handling personal data",{"label":25,"jp":51,"en":52},"[従業者]{じゅうぎょうしゃ:employee}に対する[教育]{きょういく:education}・[訓練]{くんれん:training}の[実施]{じっし:implementation}","Implementation of education and training for employees",{"label":29,"jp":54,"en":55},"[取扱]{とりあつかい:handling}[状況]{じょうきょう:status}を[確認]{かくにん:confirm}する[手段]{しゅだん:means}の[整備]{せいび:establishment}","Establishment of means to confirm handling status",{"en":57,"jp":58},"Organizational safety management measures consist of 5 items: (1) organizational structure, (2) rules for handling, (3) means to confirm handling status, (4) incident response structure, and (5) review of handling status and safety measures. Education and training for employees falls under \"human safety management measures.\"","[組織的]{そしきてき:organizational}[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}は、(1)[組織]{そしき:organization}[体制]{たいせい:structure}の[整備]{せいび:establishment}、(2)[規律]{きりつ:rules}の[整備]{せいび:establishment}、(3)[取扱]{とりあつかい:handling}[状況]{じょうきょう:status}の[確認]{かくにん:confirmation}[手段]{しゅだん:means}、(4)[漏]{ろう:leak}えい[事案]{じあん:incident}への[対応]{たいおう:response}[体制]{たいせい:structure}、(5)[取扱]{とりあつかい:handling}[状況]{じょうきょう:status}の[把握]{はあく:grasp}・[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}の[見直]{みなお:review}しの5[項目]{こうもく:items}。[従業者]{じゅうぎょうしゃ:employee}への[教育]{きょういく:education}・[訓練]{くんれん:training}は「[人的]{じんてき:human}[安全]{あんぜん:safety}[管理]{かんり:management}[措置]{そち:measures}」に[該当]{がいとう:applicable}する。",[60],"organizational-measures",{"id":62,"articleId":39,"question":63,"options":66,"correctLabel":25,"explanation":79,"tags":82},"kjh-k2-h02-q03",{"en":64,"jp":65},"Which of the following correctly defines \"employee\" (juugyousha) under the Personal Information Protection Act?","[個人情報]{こじんじょうほう:personal information}[保護法]{ほごほう:protection law}における「[従業者]{じゅうぎょうしゃ:employee}」の[定義]{ていぎ:definition}として[正]{ただ:correct}しいものはどれか。",[67,70,73,76],{"label":17,"jp":68,"en":69},"[正]{せい:regular}[社員]{しゃいん:employee}のみを[指]{さ:refer to}す","Refers only to regular (full-time) employees",{"label":21,"jp":71,"en":72},"[正]{せい:regular}[社員]{しゃいん:employee}および[契約]{けいやく:contract}[社員]{しゃいん:employee}のみを[指]{さ:refer to}す","Refers only to regular and contract employees",{"label":25,"jp":74,"en":75},"[雇用]{こよう:employment}[関係]{かんけい:relationship}にある[従業員]{じゅうぎょういん:employee}のほか、[取締役]{とりしまりやく:director}、[派遣]{はけん:dispatch}[社員]{しゃいん:worker}[等]{とう:etc.}も[含]{ふく:include}む","Includes employees in an employment relationship, as well as directors, dispatched workers, etc.",{"label":29,"jp":77,"en":78},"[業務]{ぎょうむ:business}[委託先]{いたくさき:outsourcing partner}の[社員]{しゃいん:employee}も[含]{ふく:include}む","Also includes employees of outsourcing partners",{"en":80,"jp":81},"\"Employee\" under the Act includes all persons working under the command of the business operator: regular employees, directors, executive officers, trustees, auditors, dispatched workers, etc. However, employees of outsourcing partners are NOT included.","[個人情報]{こじんじょうほう:personal information}[保護法]{ほごほう:protection law}の「[従業者]{じゅうぎょうしゃ:employee}」は、[雇用]{こよう:employment}[関係]{かんけい:relationship}にある[従業員]{じゅうぎょういん:employee}だけでなく、[取締役]{とりしまりやく:director}、[執行役]{しっこうやく:executive officer}、[理事]{りじ:trustee}、[監査役]{かんさやく:auditor}、[派遣]{はけん:dispatch}[社員]{しゃいん:worker}[等]{とう:etc.}、[事業者]{じぎょうしゃ:business operator}の[指揮]{しき:command}[命令]{めいれい:order}の[下]{もと:under}で[業務]{ぎょうむ:business}に[従事]{じゅうじ:engage}する[者]{もの:person}すべてを[含]{ふく:include}む。ただし、[委託先]{いたくさき:outsourcing partner}の[社員]{しゃいん:employee}は[含]{ふく:include}まない。",[83,84],"human-measures","employee-definition",{"id":86,"articleId":87,"question":88,"options":91,"correctLabel":29,"explanation":104,"tags":107},"kjh-k2-h02-q04","kjh-k2-h02-anzen-kanri-sochi",{"en":89,"jp":90},"Which of the following is NOT included in the three elements of outsourcing partner supervision?","[委託先]{いたくさき:outsourcing partner}の[監督]{かんとく:supervision}における3[要素]{ようそ:elements}に[含]{ふく:include}まれないものはどれか。",[92,95,98,101],{"label":17,"jp":93,"en":94},"[適切]{てきせつ:appropriate}な[委託先]{いたくさき:outsourcing partner}の[選定]{せんてい:selection}","Appropriate selection of the outsourcing partner",{"label":21,"jp":96,"en":97},"[委託]{いたく:outsourcing}[契約]{けいやく:contract}の[締結]{ていけつ:conclusion}","Conclusion of an outsourcing contract",{"label":25,"jp":99,"en":100},"[委託先]{いたくさき:outsourcing partner}における[取扱]{とりあつかい:handling}[状況]{じょうきょう:status}の[把握]{はあく:grasp}","Monitoring the handling status at the outsourcing partner",{"label":29,"jp":102,"en":103},"[委託先]{いたくさき:outsourcing partner}[社員]{しゃいん:employee}への[直接]{ちょくせつ:direct}[指揮]{しき:command}[命令]{めいれい:order}","Direct command and control of the outsourcing partner's employees",{"en":105,"jp":106},"The three elements of outsourcing partner supervision are: (1) appropriate selection, (2) conclusion of a contract, and (3) monitoring handling status. Directly commanding the outsourcing partner's employees could constitute disguised contracting (gisou ukeoi) and is not part of proper supervision.","[委託先]{いたくさき:outsourcing partner}[監督]{かんとく:supervision}の3[要素]{ようそ:elements}は、(1)[適切]{てきせつ:appropriate}な[委託先]{いたくさき:outsourcing partner}の[選定]{せんてい:selection}、(2)[委託]{いたく:outsourcing}[契約]{けいやく:contract}の[締結]{ていけつ:conclusion}、(3)[委託先]{いたくさき:outsourcing partner}における[取扱]{とりあつかい:handling}[状況]{じょうきょう:status}の[把握]{はあく:grasp}。[委託先]{いたくさき:outsourcing partner}[社員]{しゃいん:employee}への[直接]{ちょくせつ:direct}[指揮]{しき:command}[命令]{めいれい:order}は[偽装]{ぎそう:fake}[請負]{うけおい:contracting}に[該当]{がいとう:applicable}する[恐]{おそ:fear}れがあり、[監督]{かんとく:supervision}の[要素]{ようそ:element}ではない。",[108],"outsourcing-supervision",{"id":110,"articleId":87,"question":111,"options":114,"correctLabel":29,"explanation":127,"tags":130},"kjh-k2-h02-q05",{"en":112,"jp":113},"What should be done FIRST when a personal data breach occurs?","[個人]{こじん:personal}データの[漏]{ろう:leak}えい[等]{とう:etc.}が[発生]{はっせい:occur}した[場合]{ばあい:case}の[対応]{たいおう:response}フローとして[最初]{さいしょ:first}に[行]{おこな:perform}うべきことはどれか。",[115,118,121,124],{"label":17,"jp":116,"en":117},"[個人情報]{こじんじょうほう:personal information}[保護]{ほご:protection}[委員会]{いいんかい:commission}への[報告]{ほうこく:report}","Reporting to the Personal Information Protection Commission",{"label":21,"jp":119,"en":120},"[本人]{ほんにん:the individual}への[通知]{つうち:notification}","Notifying the individual",{"label":25,"jp":122,"en":123},"[事実]{じじつ:fact}[関係]{かんけい:relationship}の[調査]{ちょうさ:investigation}および[原因]{げんいん:cause}の[究明]{きゅうめい:investigation}","Investigation of the facts and root cause analysis",{"label":29,"jp":125,"en":126},"[事業者]{じぎょうしゃ:business operator}[内部]{ないぶ:internal}における[報告]{ほうこく:report}および[被害]{ひがい:damage}[拡大]{かくだい:expansion}[防止]{ぼうし:prevention}","Internal reporting and prevention of further damage",{"en":128,"jp":129},"The breach response flow is: (1) internal reporting and damage containment, (2) fact-finding and root cause analysis, (3) scope identification, (4) recurrence prevention, and (5) reporting to the PPC and notifying the individual. Internal reporting and containment come first.","[漏]{ろう:leak}えい[等]{とう:etc.}[発生]{はっせい:occurrence}[時]{じ:time}のフローは、まず(1)[事業者]{じぎょうしゃ:business operator}[内部]{ないぶ:internal}での[報告]{ほうこく:report}・[被害]{ひがい:damage}[拡大]{かくだい:expansion}[防止]{ぼうし:prevention}、(2)[事実]{じじつ:fact}[関係]{かんけい:relationship}の[調査]{ちょうさ:investigation}・[原因]{げんいん:cause}[究明]{きゅうめい:investigation}、(3)[影響]{えいきょう:impact}[範囲]{はんい:scope}の[特定]{とくてい:identification}、(4)[再発]{さいはつ:recurrence}[防止策]{ぼうしさく:prevention measures}、(5)[個人情報]{こじんじょうほう:personal information}[保護]{ほご:protection}[委員会]{いいんかい:commission}への[報告]{ほうこく:report}・[本人]{ほんにん:the individual}への[通知]{つうち:notification}の[順]{じゅん:order}で[行]{おこな:perform}う。",[131],"incident-response",{"id":133,"articleId":87,"question":134,"options":137,"correctLabel":17,"explanation":150,"tags":153},"kjh-k2-h02-q06",{"en":135,"jp":136},"In establishing the organizational structure, which position oversees the entire personal information protection system of the business operator?","[組織]{そしき:organizational}[体制]{たいせい:structure}の[整備]{せいび:establishment}において、[事業者]{じぎょうしゃ:business operator}[全体]{ぜんたい:overall}の[個人]{こじん:personal}[情報]{じょうほう:information}[保護]{ほご:protection}[体制]{たいせい:system}を[統括]{とうかつ:oversee}する[役職]{やくしょく:position}はどれか。",[138,141,144,147],{"label":17,"jp":139,"en":140},"CPO（Chief Privacy Officer）","CPO (Chief Privacy Officer)",{"label":21,"jp":142,"en":143},"[個人]{こじん:personal}[情報]{じょうほう:information}[保護]{ほご:protection}[監査]{かんさ:audit}[責任者]{せきにんしゃ:officer}","Personal Information Protection Audit Officer",{"label":25,"jp":145,"en":146},"[部門]{ぶもん:division}[長]{ちょう:manager}","Division Manager",{"label":29,"jp":148,"en":149},"[取扱]{とりあつかい:handling}[担当者]{たんとうしゃ:staff}","Handling Staff",{"en":151,"jp":152},"The CPO (Chief Privacy Officer) sits at the top and oversees the entire organization's personal information protection system. The audit officer conducts audits from a position independent of the CPO. Division managers supervise at the field level, and handling staff are the workers who actually handle personal data.","CPO（Chief Privacy Officer）は[最]{もっと:most}[上位]{じょうい:top}に[配置]{はいち:placed}され、[組織]{そしき:organization}[全体]{ぜんたい:entire}の[個人]{こじん:personal}[情報]{じょうほう:information}[保護]{ほご:protection}[体制]{たいせい:system}を[統括]{とうかつ:oversee}する。[監査]{かんさ:audit}[責任者]{せきにんしゃ:officer}はCPOから[独立]{どくりつ:independent}した[立場]{たちば:position}で[監査]{かんさ:audit}を[行う]{おこなう:perform}。[部門]{ぶもん:division}[長]{ちょう:manager}は[現場]{げんば:field}[レベル]{レベル:level}での[監督]{かんとく:supervision}、[取扱]{とりあつかい:handling}[担当者]{たんとうしゃ:staff}は[実際]{じっさい:actual}に[個人]{こじん:personal}データを[扱う]{あつかう:handle}[者]{もの:persons}である。",[154,155],"organizational-structure","CPO",{"id":157,"articleId":87,"question":158,"options":161,"correctLabel":29,"explanation":174,"tags":177},"kjh-k2-h02-q07",{"en":159,"jp":160},"Which of the following is NOT a triggering condition for the leakage reporting obligation under Article 26 of the amended Personal Information Protection Act?","[改正]{かいせい:amended}[個人]{こじん:personal}[情報]{じょうほう:information}[保護法]{ほごほう:Protection Act}[第]{だい:Article}26[条]{じょう:article}における[漏]{ろう:leak}えい[等]{とう:etc.}[報告]{ほうこく:report}[義務]{ぎむ:obligation}の[対象]{たいしょう:subject}[要件]{ようけん:requirement}に[該当]{がいとう:applicable}しないものはどれか。",[162,165,168,171],{"label":17,"jp":163,"en":164},"[要]{よう:requiring}[配慮]{はいりょ:consideration}[個人]{こじん:personal}[情報]{じょうほう:information}の[漏]{ろう:leak}えい","Leakage of specially-care-required personal information",{"label":21,"jp":166,"en":167},"[不正]{ふせい:unauthorized}[利用]{りよう:use}による[財産的]{ざいさんてき:property}[被害]{ひがい:damage}の[恐]{おそ:fear}れがある[漏]{ろう:leak}えい","Leakage that may cause property damage through unauthorized use",{"label":25,"jp":169,"en":170},"[不正]{ふせい:unauthorized}な[目的]{もくてき:purpose}による[恐]{おそ:fear}れがある[漏]{ろう:leak}えい","Leakage suspected of being for unauthorized purposes",{"label":29,"jp":172,"en":173},"100[人]{にん:persons}を[超]{こ:exceed}える[漏]{ろう:leak}えい","Leakage exceeding 100 individuals",{"en":175,"jp":176},"The numerical threshold is \"leakage exceeding 1,000 persons,\" not 100. The other three are all conditions that mandate reporting to the PPC and notifying the individual. Reporting is in two stages: preliminary report (within 3-5 days of discovery) and definitive report (within 30 days; 60 days for unauthorized-purpose cases).","[数]{かず:numerical}[的]{てき:-ical}[要件]{ようけん:requirement}は「1,000[人]{にん:persons}を[超]{こ:exceed}える[漏]{ろう:leak}えい」であり、100[人]{にん:persons}ではない。[他]{ほか:other}の3つはすべてPPCへの[報告]{ほうこく:report}・[本人]{ほんにん:individual}[通知]{つうち:notification}が[義務]{ぎむ:mandatory}づけられる[要件]{ようけん:condition}。[報告]{ほうこく:report}は[速報]{そくほう:preliminary report}（[発見]{はっけん:discovery}から3〜5[日]{にち:days}[以内]{いない:within}）と[確報]{かくほう:definitive report}（30[日]{にち:days}[以内]{いない:within}、[不正]{ふせい:unauthorized}[目的]{もくてき:purpose}は60[日]{にち:days}）の2[段階]{だんかい:stages}で[行う]{おこなう:made}。",[178,179],"breach-reporting","article-26",{"id":181,"articleId":87,"question":182,"options":185,"correctLabel":29,"explanation":198,"tags":201},"kjh-k2-h02-q08",{"en":183,"jp":184},"Which of the following is NOT an appropriate point in time to conclude or confirm a non-disclosure agreement (NDA)?","[秘密]{ひみつ:secret}[保持]{ほじ:maintenance}[契約]{けいやく:contract}（NDA）の[締結]{ていけつ:conclusion}[時]{じ:time}[点]{てん:point}として[適切]{てきせつ:appropriate}でないものはどれか。",[186,189,192,195],{"label":17,"jp":187,"en":188},"[入社]{にゅうしゃ:joining the company}[時]{じ:time}に[誓約書]{せいやくしょ:pledge}を[提出]{ていしゅつ:submit}させる","Submitting a pledge upon joining the company",{"label":21,"jp":190,"en":191},"[部署]{ぶしょ:department}[異動]{いどう:transfer}[時]{じ:time}に[再度]{さいど:again}[確認]{かくにん:confirm}する","Re-confirming upon department transfer",{"label":25,"jp":193,"en":194},"[退職]{たいしょく:resignation}[時]{じ:time}に[退職]{たいしょく:after leaving}[後]{ご:after}も[継続]{けいぞく:continuing}する[守秘]{しゅひ:confidentiality}[義務]{ぎむ:obligation}を[書面]{しょめん:in writing}で[確認]{かくにん:confirm}する","Confirming the continuing post-resignation confidentiality obligation in writing at resignation",{"label":29,"jp":196,"en":197},"[採用]{さいよう:hiring}[面接]{めんせつ:interview}の[段階]{だんかい:stage}で[応募者]{おうぼしゃ:applicant}[全員]{ぜんいん:all}に[締結]{ていけつ:conclude}させる","Requiring all applicants to sign at the recruitment interview stage",{"en":199,"jp":200},"NDAs are concluded and confirmed at three points: joining, department transfer, and resignation. At the recruitment interview stage, no employment relationship exists yet, so it would lack effectiveness. Provisions should also be in employment rules, with disciplinary actions for violations clearly stated.","NDAは[入社]{にゅうしゃ:joining}[時]{じ:time}・[部署]{ぶしょ:department}[異動]{いどう:transfer}[時]{じ:time}・[退職]{たいしょく:resignation}[時]{じ:time}の3つの[時点]{じてん:points in time}で[締結]{ていけつ:concluded}・[確認]{かくにん:confirmed}する。[採用]{さいよう:recruitment}[面接]{めんせつ:interview}[段階]{だんかい:stage}では[雇用]{こよう:employment}[関係]{かんけい:relationship}が[成立]{せいりつ:established}しておらず[実効性]{じっこうせい:effectiveness}に[乏しい]{とぼしい:lacking}。[就業]{しゅうぎょう:employment}[規則]{きそく:rules}にも[規定]{きてい:provisions}を[設け]{もうけ:establish}、[違反]{いはん:violation}[時]{じ:case}の[懲戒]{ちょうかい:disciplinary}[処分]{しょぶん:action}を[明記]{めいき:state}する。",[202,203],"NDA","confidentiality",{"id":205,"articleId":87,"question":206,"options":209,"correctLabel":21,"explanation":222,"tags":225},"kjh-k2-h02-q09",{"en":207,"jp":208},"Which of the following correctly describes internal audits?","[内部]{ないぶ:internal}[監査]{かんさ:audit}についての[説明]{せつめい:explanation}として[正]{ただ:correct}しいものはどれか。",[210,213,216,219],{"label":17,"jp":211,"en":212},"[監査]{かんさ:audit}は[被]{ひ:audited}[監査]{かんさ:audit}[部門]{ぶもん:department}と[同]{おな:same}じ[部門]{ぶもん:department}が[実施]{じっし:conduct}する","Audits are conducted by the same department as the audited department",{"label":21,"jp":214,"en":215},"PDCAサイクルの「Check」と「Act」に[該当]{がいとう:correspond}し、[年]{ねん:year}に1[回]{かい:time}[以上]{いじょう:or more}[実施]{じっし:conduct}するのが[望]{のぞ:desirable}ましい","Corresponds to \"Check\" and \"Act\" in the PDCA cycle and is desirable to conduct at least once per year",{"label":25,"jp":217,"en":218},"[監査]{かんさ:audit}[結果]{けっか:results}は[機密]{きみつ:confidential}[性]{せい:-ity}[保持]{ほじ:maintenance}のため[経営]{けいえい:management}[層]{そう:level}には[報告]{ほうこく:report}しない","Audit results are not reported to management for confidentiality reasons",{"label":29,"jp":220,"en":221},"[外部]{がいぶ:external}[環境]{かんきょう:environment}の[変化]{へんか:change}は[監査]{かんさ:audit}や[見直し]{みなおし:review}には[影響]{えいきょう:influence}しない","External environment changes do not affect audits or reviews",{"en":223,"jp":224},"Internal audits correspond to \"Check\" and \"Act\" in PDCA and are desirably conducted at least once a year. Audits must be conducted objectively from an independent position (audit officer independent of the CPO). Results are reported to management, with corrective measures taken. Reviews are conducted in response to legal amendments and new threats.","[内部]{ないぶ:internal}[監査]{かんさ:audit}はPDCAの「Check（[点検]{てんけん:check}）」「Act（[改善]{かいぜん:improvement}）」に[該当]{がいとう:corresponds}し、[年]{ねん:year}1[回]{かい:time}[以上]{いじょう:or more}が[望]{のぞ:desired}ましい。[監査]{かんさ:audit}は[独立]{どくりつ:independent}した[立場]{たちば:position}（CPOから[独立]{どくりつ:independent}した[監査]{かんさ:audit}[責任者]{せきにんしゃ:officer}）から[客観的]{きゃっかんてき:objectively}に[行う]{おこなう:conducted}必要があり、[結果]{けっか:results}は[経営]{けいえい:management}[層]{そう:level}に[報告]{ほうこく:report}し[是正]{ぜせい:corrective}[措置]{そち:measures}を[講]{こう:take}じる。[法令]{ほうれい:legal}[改正]{かいせい:amendments}や[新た]{あらた:new}な[脅威]{きょうい:threats}に[応]{おう:in response to}じて[見直]{みなお:review}しを[行う]{おこなう:conducted}。",[226,227],"internal-audit","PDCA",{"id":229,"articleId":11,"question":230,"options":233,"correctLabel":21,"explanation":246,"tags":249},"kjh-k2-h02-q10",{"en":231,"jp":232},"In the hierarchical document structure for personal information protection, which document is at the highest level?","[個人]{こじん:personal}[情報]{じょうほう:information}[保護]{ほご:protection}に[関]{かん:related}する[規程]{きてい:regulation}[文書]{ぶんしょ:documents}の[階層]{かいそう:hierarchy}[構造]{こうぞう:structure}において、[最上位]{さいじょうい:highest level}に[位置]{いち:positioned}するのはどれか。",[234,237,240,243],{"label":17,"jp":235,"en":236},"[実施]{じっし:implementation}[手順書]{てじゅんしょ:procedure manual}・マニュアル","Implementation procedure manuals",{"label":21,"jp":238,"en":239},"[基本]{きほん:basic}[方針]{ほうしん:policy}（プライバシーポリシー）","Basic policy (privacy policy)",{"label":25,"jp":241,"en":242},"[個人]{こじん:personal}[情報]{じょうほう:information}[保護]{ほご:protection}[規程]{きてい:regulation}（[管理]{かんり:management}[規程]{きてい:regulation}）","Personal information protection regulations (management regulations)",{"label":29,"jp":244,"en":245},"[様式]{ようしき:forms}・[記録]{きろく:records}（[申請書]{しんせいしょ:application forms}・[台帳]{だいちょう:ledgers}）","Forms and records (application forms, ledgers)",{"en":247,"jp":248},"The document system has 4 tiers: highest = basic policy (privacy policy); second = protection regulations; third = implementation procedure manuals; fourth = forms and records. Higher-level documents show organizational intent; lower-level documents stipulate concrete operations.","[文書]{ぶんしょ:document}[体系]{たいけい:system}は4[層]{そう:tiers}：[最上位]{さいじょうい:highest}＝[基本]{きほん:basic}[方針]{ほうしん:policy}（プライバシーポリシー）、[第二]{だいに:second}[層]{そう:layer}＝[保護]{ほご:protection}[規程]{きてい:regulation}、[第三]{だいさん:third}[層]{そう:layer}＝[実施]{じっし:implementation}[手順書]{てじゅんしょ:procedure manual}、[第四]{だいよん:fourth}[層]{そう:layer}＝[様式]{ようしき:forms}・[記録]{きろく:records}。[上位]{じょうい:higher}[文書]{ぶんしょ:documents}は[組織]{そしき:organization}の[意思]{いし:intent}を[示し]{しめし:show}、[下位]{かい:lower}[文書]{ぶんしょ:documents}は[具体的]{ぐたいてき:concrete}な[運用]{うんよう:operation}を[規定]{きてい:stipulate}する。",[250,251],"policy-hierarchy","privacy-policy",{"id":253,"articleId":11,"question":254,"options":257,"correctLabel":21,"explanation":270,"tags":273},"kjh-k2-h02-q11",{"en":255,"jp":256},"Which is the correct formula for calculating ALE (Annual Loss Expectancy) in quantitative risk analysis?","[定量的]{ていりょうてき:quantitative}リスク[分析]{ぶんせき:analysis}における ALE（Annual Loss Expectancy）の[計算]{けいさん:calculation}[式]{しき:formula}として[正]{ただ:correct}しいものはどれか。",[258,261,264,267],{"label":17,"jp":259,"en":260},"ALE ＝ [脅威]{きょうい:threat} × [脆弱性]{ぜいじゃくせい:vulnerability}","ALE = Threat x Vulnerability",{"label":21,"jp":262,"en":263},"ALE ＝ SLE × ARO","ALE = SLE x ARO",{"label":25,"jp":265,"en":266},"ALE ＝ [資産]{しさん:asset}[価値]{かち:value} ÷ [発生]{はっせい:occurrence}[頻度]{ひんど:frequency}","ALE = Asset Value \u002F Occurrence Frequency",{"label":29,"jp":268,"en":269},"ALE ＝ [被害]{ひがい:damage}[額]{がく:amount} ＋ [対策]{たいさく:countermeasure}[費用]{ひよう:cost}","ALE = Damage Amount + Countermeasure Cost",{"en":271,"jp":272},"ALE (Annual Loss Expectancy) = SLE (Single Loss Expectancy) x ARO (Annualized Rate of Occurrence). Example: if a single leak causes 5 million yen damage and occurs 0.1 times\u002Fyear, ALE = 500,000 yen. Qualitative analysis uses level ratings like \"high\u002Fmedium\u002Flow.\"","ALE（Annual Loss Expectancy、[年間]{ねんかん:annual}[予想]{よそう:expected}[損失額]{そんしつがく:loss amount}）＝SLE（Single Loss Expectancy、1[回]{かい:one}[当]{あ:per}たりの[損失額]{そんしつがく:loss amount}）×ARO（Annualized Rate of Occurrence、[年間]{ねんかん:annual}[発生]{はっせい:occurrence}[頻度]{ひんど:frequency}）。[例]{れい:example}：1[回]{かい:one}の[漏]{ろう:leak}えいで500[万]{まん:10,000}[円]{えん:yen}の[被害]{ひがい:damage}が[予想]{よそう:expected}され、[年]{ねん:year}0.1[回]{かい:times}[発生]{はっせい:occur}するなら、ALE＝50[万]{まん:10,000}[円]{えん:yen}。[定性的]{ていせいてき:qualitative}[分析]{ぶんせき:analysis}は「[高]{こう:high}・[中]{ちゅう:medium}・[低]{てい:low}」のレベル[評価]{ひょうか:evaluation}である。",[274,275,276],"risk-analysis","quantitative","ALE",{"id":278,"articleId":87,"question":279,"options":282,"correctLabel":21,"explanation":295,"tags":298},"kjh-k2-h02-q12",{"en":280,"jp":281},"What may a situation be considered when an outsourcer directly commands the outsourcing partner's employees?","[委託先]{いたくさき:outsourcing partner}[社員]{しゃいん:employee}を[委託元]{いたくもと:outsourcer}[企業]{きぎょう:company}が[直接]{ちょくせつ:directly}[指揮]{しき:command}[命令]{めいれい:order}した[場合]{ばあい:case}に[該当]{がいとう:applicable}する[恐]{おそ:concern}れがあるものはどれか。",[283,286,289,292],{"label":17,"jp":284,"en":285},"[適法]{てきほう:legal}な[業務]{ぎょうむ:business}[委託]{いたく:outsourcing}","Legal business outsourcing",{"label":21,"jp":287,"en":288},"[偽装]{ぎそう:disguised}[請負]{うけおい:contracting}","Disguised contracting (gisou ukeoi)",{"label":25,"jp":290,"en":291},"[再]{さい:sub-}[委託]{いたく:outsourcing}","Subcontracting",{"label":29,"jp":293,"en":294},"[労働]{ろうどう:labor}[者]{しゃ:worker}[派遣]{はけん:dispatch}","Worker dispatch",{"en":296,"jp":297},"Under a business outsourcing (contracting) agreement, command and control of the outsourcing partner's employees should be performed by the outsourcing partner company. If the outsourcer directly commands them, the actual situation is no different from worker dispatch and may constitute \"disguised contracting\" (gisou ukeoi), which violates the Worker Dispatch Act.","[業務]{ぎょうむ:business}[委託]{いたく:outsourcing}（[請負]{うけおい:contracting}）[契約]{けいやく:contract}では、[委託先]{いたくさき:outsourcing partner}[社員]{しゃいん:employee}への[指揮]{しき:command}[命令]{めいれい:order}は[委託先]{いたくさき:outsourcing partner}[企業]{きぎょう:company}が[行う]{おこなう:perform}べき。[委託元]{いたくもと:outsourcer}が[直接]{ちょくせつ:directly}[指揮]{しき:command}[命令]{めいれい:order}すると[実態]{じったい:reality}は[労働]{ろうどう:labor}[者]{しゃ:worker}[派遣]{はけん:dispatch}と[変]{か:change}わらず、「[偽装]{ぎそう:disguised}[請負]{うけおい:contracting}」に[該当]{がいとう:applicable}する[恐]{おそ:fear}れがあり、[労働]{ろうどう:labor}[者]{しゃ:worker}[派遣法]{はけんほう:Dispatch Act}[違反]{いはん:violation}となる。",[108,299],"gisou-ukeoi",{"id":301,"articleId":87,"question":302,"options":305,"correctLabel":21,"explanation":318,"tags":321},"kjh-k2-h02-q13",{"en":303,"jp":304},"Which is the correct deadline (in principle) for submitting the \"definitive report\" (kakuhou) under the amended Personal Information Protection Act after a leak?","[改正]{かいせい:amended}[個人]{こじん:personal}[情報]{じょうほう:information}[保護法]{ほごほう:Protection Act}における[漏]{ろう:leak}えい[時]{じ:time}の「[確報]{かくほう:definitive report}」の[提出]{ていしゅつ:submission}[期限]{きげん:deadline}（[原則]{げんそく:in principle}）として[正]{ただ:correct}しいものはどれか。",[306,309,312,315],{"label":17,"jp":307,"en":308},"[発見]{はっけん:discovery}から3〜5[日]{にち:days}[以内]{いない:within}","Within 3-5 days of discovery",{"label":21,"jp":310,"en":311},"[発見]{はっけん:discovery}から30[日]{にち:days}[以内]{いない:within}","Within 30 days of discovery",{"label":25,"jp":313,"en":314},"[発見]{はっけん:discovery}から60[日]{にち:days}[以内]{いない:within}","Within 60 days of discovery",{"label":29,"jp":316,"en":317},"[発見]{はっけん:discovery}から90[日]{にち:days}[以内]{いない:within}","Within 90 days of discovery",{"en":319,"jp":320},"Reporting to the PPC after a leak is in two stages: preliminary report = within 3-5 days of discovery (outline), definitive report = within 30 days (including cause and recurrence prevention measures). However, for leaks with unauthorized purposes, the deadline is extended to within 60 days.","[漏]{ろう:leak}えい[時]{じ:time}のPPCへの[報告]{ほうこく:report}は2[段階]{だんかい:stages}：[速報]{そくほう:preliminary report}＝[発見]{はっけん:discovery}から3〜5[日]{にち:days}[以内]{いない:within}（[概要]{がいよう:outline}）、[確報]{かくほう:definitive report}＝30[日]{にち:days}[以内]{いない:within}（[原因]{げんいん:cause}・[再発]{さいはつ:recurrence}[防止]{ぼうし:prevention}[策]{さく:measures}まで[含]{ふく:include}む）。ただし[不正]{ふせい:unauthorized}な[目的]{もくてき:purpose}による[漏]{ろう:leak}えいは60[日]{にち:days}[以内]{いない:within}と[期限]{きげん:deadline}が[延長]{えんちょう:extended}される。",[178,322],"kakuhou",{"culture-anime-studio-ghibli":324,"culture-bonsai-art":328,"tech-cybozu-kintone-no-code":332,"living-denki-gas-suidou":336,"tech-gree-mobile-game-ops":340,"culture-green-tea-types":344,"living-gym-fitness":348,"living-internet-hikari":352,"living-jisha-de-kau":356,"exam-jlpt-n3-grammar":360,"exam-jlpt-n3-vocab":364,"bj-job-gata-koyou":368,"culture-kabuki-noh-bunraku":372,"bj-karoushi-hatarakikata":376,"living-keitai-mobile-plan":380,"living-konbini-atm-banking":384,"living-kosodate-hoiku":388,"culture-nihon-teien":392,"bj-nomikai-survival":396,"tech-pixiv-image-cdn":400,"culture-sake-shochu":404,"bj-sankyu-ikukyu":408,"tech-sansan-eight-platform":412,"culture-shichi-go-san":416,"bj-shukatsu-shinsotsu":420,"tech-smartnews-recommendation":424,"bj-taishoku-todoke":428,"bj-telework-policy":432,"bj-tenshoku-resume":436,"tech-yahoo-japan-search":440,"culture-anime-business":444,"exam-ap":448,"exam-aws-japan":452,"law-chosakuken":456,"tech-cookpad-recipe-search":460,"tech-cybozu-kintone-api":464,"tech-dena-observability":468,"law-denshi-chouho":472,"tech-digital-cho-cloud":476,"exam-fe":480,"tech-freee-accounting":484,"law-furiransu-hou":488,"law-harassment":492,"tech-hatena-mackerel":496,"bj-hourensou":500,"bj-hyouka-mendan":504,"law-invoice":508,"exam-it-passport":512,"culture-izakaya":516,"culture-j-league":520,"culture-jinja-tera":524,"exam-jlpt-n1-dokkai":528,"exam-jlpt-n2-business":532,"bj-kaigi-manner":536,"living-kakutei-shinkoku":540,"bj-keigo-kihon":544,"law-keihin-hyouji":548,"living-kenkou-hoken":552,"living-kosei-nenkin":556,"tech-line-llmops":560,"tech-line-streaming":564,"living-chintai-keiyaku":568,"living-eijuken":572,"living-engineer-visa":576,"living-ginkou-koza":580,"living-hikkoshi-checklist":584,"living-koudo-senmon":588,"culture-matsuri":592,"bj-meishi-koukan":596,"tech-mercari-merpay-id":600,"tech-mercari-microservices":604,"tech-mf-multitenant":608,"bj-nemawashi-ringi":612,"living-nenmatsu-chousei":616,"bj-1on1":620,"bj-online-kaigi":624,"culture-onsen":628,"culture-pro-baseball":632,"culture-ramen":636,"tech-recruit-data-platform":640,"law-roukikihou-kihon":644,"culture-sado":648,"culture-sandou":652,"culture-seasonal-events":656,"exam-sg":660,"bj-shagai-mail":664,"bj-shanai-mail":668,"culture-sumo":672,"culture-sushi":676,"culture-washoku":680,"law-yuukyuu-kyuuka":684,"kjh-k1-h04-anzen-kanri":688,"bill-one-auth":691,"contract-one-vision":695,"kjh-k1-h04-daisan-sha-teikyou":699,"eight-web-renewal":703,"kjh-k1-h04-gaikoku-kiroku":707,"kjh-k2-h04-gijutsu-jisshi":711,"kjh-k2-h04-gijutsu-kiso":715,"kjh-k1-h01-hotaikei":719,"kjh-k1-h06-hoyu-data":723,"kjh-k1-h07-kamei-kakou":727,"kjh-k1-h05-kanren-joho":731,"kjh-k1-h02-kihon-rinen":735,"kjh-k1-h09-jikkousei":739,"kjh-k1-h10-gyousei":743,"kjh-k1-h11-my-number-hogo":747,"kjh-k1-h11-my-number-sousoku":751,"kjh-k2-h01-guideline":755,"kjh-k2-h01-security-kiso":759,"kjh-k2-h02-anzen-kanri-sochi":763,"kjh-k2-h02-soshiki-kiso":766,"kjh-k2-h03-office":769,"kjh-k1-h03-riyou-mokuteki":773,"sansan-data-intelligence":777,"sansan-engineer-team-infra":781,"sansan-honne-15":785,"sansan-interview-110":789,"sansan-interview-126":793,"sansan-interview-127":797,"sansan-interview-130":801,"sansan-interview-40":805,"sansan-oyaco":809,"kjh-k1-h03-tekisei-shutoku":813,"kjh-k1-h08-tokumei-kakou":817},{"articleId":325,"path":326,"title":327},"culture-anime-studio-ghibli","\u002Farticles\u002Fculture\u002Fanime-studio-ghibli","スタジオジブリ作品史 — 宮崎駿・高畑勲・鈴木敏夫が築いた40年",{"articleId":329,"path":330,"title":331},"culture-bonsai-art","\u002Farticles\u002Fculture\u002Fbonsai-art","盆栽の世界 — 小宇宙を育てる日本の芸術",{"articleId":333,"path":334,"title":335},"tech-cybozu-kintone-no-code","\u002Farticles\u002Ftech\u002Fcybozu-kintone-no-code","kintoneのローコード戦略 — 業務アプリを誰でも作れる仕組み",{"articleId":337,"path":338,"title":339},"living-denki-gas-suidou","\u002Farticles\u002Fliving-in-japan\u002Fdenki-gas-suidou","電気・ガス・水道の契約 — 引越し時のライフライン手続き",{"articleId":341,"path":342,"title":343},"tech-gree-mobile-game-ops","\u002Farticles\u002Ftech\u002Fgree-mobile-game-ops","GREEのモバイルゲーム運用 — リアルタイム対戦と決済の裏側",{"articleId":345,"path":346,"title":347},"culture-green-tea-types","\u002Farticles\u002Fculture\u002Fgreen-tea-types","日本茶の種類と淹れ方 — 煎茶・玉露・抹茶の違い",{"articleId":349,"path":350,"title":351},"living-gym-fitness","\u002Farticles\u002Fliving-in-japan\u002Fgym-fitness","ジムとフィットネスクラブ — 入会から解約までの実務ガイド",{"articleId":353,"path":354,"title":355},"living-internet-hikari","\u002Farticles\u002Fliving-in-japan\u002Finternet-hikari-keiyaku","光回線とネット契約 — フレッツ・NURO・auひかり比較",{"articleId":357,"path":358,"title":359},"living-jisha-de-kau","\u002Farticles\u002Fliving-in-japan\u002Fjisha-de-kau","日本で不動産を買う — 外国人でも住宅ローンを組む方法",{"articleId":361,"path":362,"title":363},"exam-jlpt-n3-grammar","\u002Farticles\u002Fexams\u002Fjlpt-n3-grammar","JLPT N3 文法 — 初級から中級への橋渡し",{"articleId":365,"path":366,"title":367},"exam-jlpt-n3-vocab","\u002Farticles\u002Fexams\u002Fjlpt-n3-vocab","JLPT N3 語彙対策 — 1500語をどう攻略するか",{"articleId":369,"path":370,"title":371},"bj-job-gata-koyou","\u002Farticles\u002Fbusiness-japanese\u002Fjob-gata-koyou","ジョブ型雇用への移行 — メンバーシップ型からの脱却",{"articleId":373,"path":374,"title":375},"culture-kabuki-noh-bunraku","\u002Farticles\u002Fculture\u002Fkabuki-noh-bunraku","歌舞伎・能・文楽 — 日本三大伝統演劇の世界",{"articleId":377,"path":378,"title":379},"bj-karoushi-hatarakikata","\u002Farticles\u002Fbusiness-japanese\u002Fkaroushi-hatarakikata","過労死と働き方改革 — 残業規制の歴史と現状",{"articleId":381,"path":382,"title":383},"living-keitai-mobile-plan","\u002Farticles\u002Fliving-in-japan\u002Fkeitai-mobile-plan","携帯電話契約の選び方 — 大手キャリア・MVNO・eSIM完全ガイド",{"articleId":385,"path":386,"title":387},"living-konbini-atm-banking","\u002Farticles\u002Fliving-in-japan\u002Fkonbini-atm-banking","コンビニATMと電子マネー — 現金とキャッシュレスのハイブリッド生活",{"articleId":389,"path":390,"title":391},"living-kosodate-hoiku","\u002Farticles\u002Fliving-in-japan\u002Fkosodate-hoiku","子育て支援と保育園 — 児童手当・保活・無償化制度",{"articleId":393,"path":394,"title":395},"culture-nihon-teien","\u002Farticles\u002Fculture\u002Fnihon-teien","日本庭園の世界 — 池泉・枯山水・露地の様式",{"articleId":397,"path":398,"title":399},"bj-nomikai-survival","\u002Farticles\u002Fbusiness-japanese\u002Fnomikai-survival","飲み会・ノミニケーション完全攻略 — 新人エンジニアのサバイバルガイド",{"articleId":401,"path":402,"title":403},"tech-pixiv-image-cdn","\u002Farticles\u002Ftech\u002Fpixiv-image-cdn","pixivの画像配信基盤 — 数億イラストを世界に届ける技術",{"articleId":405,"path":406,"title":407},"culture-sake-shochu","\u002Farticles\u002Fculture\u002Fsake-shochu","日本酒と焼酎入門 — 製法・産地・飲み方の基礎",{"articleId":409,"path":410,"title":411},"bj-sankyu-ikukyu","\u002Farticles\u002Fbusiness-japanese\u002Fsankyu-ikukyu","産休・育休制度の実務 — 取得スケジュールと給付金",{"articleId":413,"path":414,"title":415},"tech-sansan-eight-platform","\u002Farticles\u002Ftech\u002Fsansan-eight-platform","Eight 名刺SaaSの基盤進化 — モバイルから法人向けプラットフォームへ",{"articleId":417,"path":418,"title":419},"culture-shichi-go-san","\u002Farticles\u002Fculture\u002Fshichi-go-san","七五三 — 子供の成長を祝う伝統行事",{"articleId":421,"path":422,"title":423},"bj-shukatsu-shinsotsu","\u002Farticles\u002Fbusiness-japanese\u002Fshukatsu-shinsotsu","新卒就活の流れ — エントリーシートから内定まで",{"articleId":425,"path":426,"title":427},"tech-smartnews-recommendation","\u002Farticles\u002Ftech\u002Fsmartnews-recommendation","SmartNewsの推薦システム — ニュースを最適化する機械学習",{"articleId":429,"path":430,"title":431},"bj-taishoku-todoke","\u002Farticles\u002Fbusiness-japanese\u002Ftaishoku-todoke","退職届と退職願 — 違いと書き方、円満退職への手順",{"articleId":433,"path":434,"title":435},"bj-telework-policy","\u002Farticles\u002Fbusiness-japanese\u002Ftelework-policy","テレワーク制度の現状 — コロナ後の在宅勤務とハイブリッド",{"articleId":437,"path":438,"title":439},"bj-tenshoku-resume","\u002Farticles\u002Fbusiness-japanese\u002Ftenshoku-resume","転職活動の進め方 — 履歴書と職務経歴書の書き方",{"articleId":441,"path":442,"title":443},"tech-yahoo-japan-search","\u002Farticles\u002Ftech\u002Fyahoo-japan-search","Yahoo! JAPAN検索の基盤 — 日本語特化の大規模検索システム",{"articleId":445,"path":446,"title":447},"culture-anime-business","\u002Farticles\u002Fculture\u002Fanime-business","アニメ・漫画文化と産業構造 — グローバル展開の現状",{"articleId":449,"path":450,"title":451},"exam-ap","\u002Farticles\u002Fexams\u002Fap","応用情報技術者試験 — 重点出題分野",{"articleId":453,"path":454,"title":455},"exam-aws-japan","\u002Farticles\u002Fexams\u002Faws-japan","AWS認定 — 日本語受験のコツ",{"articleId":457,"path":458,"title":459},"law-chosakuken","\u002Farticles\u002Flaw\u002Fchosakuken","著作権法 — エンジニアが知っておくべき基礎",{"articleId":461,"path":462,"title":463},"tech-cookpad-recipe-search","\u002Farticles\u002Ftech\u002Fcookpad-recipe-search-ranking","Cookpadのレシピ検索 — 学習to-rank実装",{"articleId":465,"path":466,"title":467},"tech-cybozu-kintone-api","\u002Farticles\u002Ftech\u002Fcybozu-kintone-api-design","kintone API設計の十年 — 後方互換性との戦い",{"articleId":469,"path":470,"title":471},"tech-dena-observability","\u002Farticles\u002Ftech\u002Fdena-mobile-game-observability","DeNAのモバイルゲーム監視基盤",{"articleId":473,"path":474,"title":475},"law-denshi-chouho","\u002Farticles\u002Flaw\u002Fdenshi-chouho","電子帳簿保存法 — スキャナ保存と電子取引保存の対応",{"articleId":477,"path":478,"title":479},"tech-digital-cho-cloud","\u002Farticles\u002Ftech\u002Fdigital-cho-government-cloud","デジタル庁ガバメントクラウド技術詳細",{"articleId":481,"path":482,"title":483},"exam-fe","\u002Farticles\u002Fexams\u002Ffe","基本情報技術者試験 — シラバス全体像",{"articleId":485,"path":486,"title":487},"tech-freee-accounting","\u002Farticles\u002Ftech\u002Ffreee-accounting-integrity","freeeの会計データ整合性 — 仕訳バランスの自動検証",{"articleId":489,"path":490,"title":491},"law-furiransu-hou","\u002Farticles\u002Flaw\u002Ffuriransu-hou","フリーランス保護法（2024年施行）— 取引適正化のポイント",{"articleId":493,"path":494,"title":495},"law-harassment","\u002Farticles\u002Flaw\u002Fharassment","ハラスメント関連法 — パワハラ・セクハラ・マタハラ防止義務",{"articleId":497,"path":498,"title":499},"tech-hatena-mackerel","\u002Farticles\u002Ftech\u002Fhatena-mackerel-alert-design","MackerelのAlert設計思想",{"articleId":501,"path":502,"title":503},"bj-hourensou","\u002Farticles\u002Fbusiness-japanese\u002Fhourensou","報・連・相 — 日本企業のコミュニケーションの基本",{"articleId":505,"path":506,"title":507},"bj-hyouka-mendan","\u002Farticles\u002Fbusiness-japanese\u002Fhyouka-mendan","評価面談の準備と振り返り",{"articleId":509,"path":510,"title":511},"law-invoice","\u002Farticles\u002Flaw\u002Finvoice-seido","インボイス制度の仕組みと実務 — 適格請求書発行事業者",{"articleId":513,"path":514,"title":515},"exam-it-passport","\u002Farticles\u002Fexams\u002Fit-passport","ITパスポート試験 — 概要と学習法",{"articleId":517,"path":518,"title":519},"culture-izakaya","\u002Farticles\u002Fculture\u002Fizakaya","居酒屋文化と乾杯のマナー — お通しから締めまで",{"articleId":521,"path":522,"title":523},"culture-j-league","\u002Farticles\u002Fculture\u002Fj-league","Jリーグの歴史と地域密着 — 1993年開幕から30年",{"articleId":525,"path":526,"title":527},"culture-jinja-tera","\u002Farticles\u002Fculture\u002Fjinja-tera","神社と寺の違い、参拝マナー",{"articleId":529,"path":530,"title":531},"exam-jlpt-n1-dokkai","\u002Farticles\u002Fexams\u002Fjlpt-n1-dokkai","JLPT N1 — 読解問題のアプローチ",{"articleId":533,"path":534,"title":535},"exam-jlpt-n2-business","\u002Farticles\u002Fexams\u002Fjlpt-n2-business","JLPT N2 — ビジネス語彙集中対策",{"articleId":537,"path":538,"title":539},"bj-kaigi-manner","\u002Farticles\u002Fbusiness-japanese\u002Fkaigi-manner","会議のマナーと進め方 — 司会から議事録まで",{"articleId":541,"path":542,"title":543},"living-kakutei-shinkoku","\u002Farticles\u002Fliving-in-japan\u002Fkakutei-shinkoku","確定申告の基本 — 給与所得・副業・控除",{"articleId":545,"path":546,"title":547},"bj-keigo-kihon","\u002Farticles\u002Fbusiness-japanese\u002Fkeigo-kihon","ビジネス敬語の基本 — 尊敬語・謙譲語・丁寧語の使い分け",{"articleId":549,"path":550,"title":551},"law-keihin-hyouji","\u002Farticles\u002Flaw\u002Fkeihin-hyouji","改正景品表示法とステマ規制 — マーケティングの法的注意点",{"articleId":553,"path":554,"title":555},"living-kenkou-hoken","\u002Farticles\u002Fliving-in-japan\u002Fkenkou-hoken","健康保険の入門 — 国保と社保の違い",{"articleId":557,"path":558,"title":559},"living-kosei-nenkin","\u002Farticles\u002Fliving-in-japan\u002Fkosei-nenkin","厚生年金と国民年金 — 老後の備えと現役の負担",{"articleId":561,"path":562,"title":563},"tech-line-llmops","\u002Farticles\u002Ftech\u002Fline-llmops","LINEのLLMOps — 大規模言語モデル運用の取り組み",{"articleId":565,"path":566,"title":567},"tech-line-streaming","\u002Farticles\u002Ftech\u002Fline-streaming","LINEの大規模リアルタイム配信基盤",{"articleId":569,"path":570,"title":571},"living-chintai-keiyaku","\u002Farticles\u002Fliving-in-japan\u002Fliving-chintai-keiyaku","賃貸契約と保証会社 — 礼金・敷金から保証料まで",{"articleId":573,"path":574,"title":575},"living-eijuken","\u002Farticles\u002Fliving-in-japan\u002Fliving-eijuken","永住権申請の最新基準 — 一般・高度専門職ルート比較",{"articleId":577,"path":578,"title":579},"living-engineer-visa","\u002Farticles\u002Fliving-in-japan\u002Fliving-engineer-visa","エンジニアの在留資格 — 「技術・人文知識・国際業務」ビザの取得手順",{"articleId":581,"path":582,"title":583},"living-ginkou-koza","\u002Farticles\u002Fliving-in-japan\u002Fliving-ginkou-koza","銀行口座開設とクレジットカード — 外国人エンジニアの実務",{"articleId":585,"path":586,"title":587},"living-hikkoshi-checklist","\u002Farticles\u002Fliving-in-japan\u002Fliving-hikkoshi-checklist","引越し手続きチェックリスト — 役所・ライフライン・住所変更",{"articleId":589,"path":590,"title":591},"living-koudo-senmon","\u002Farticles\u002Fliving-in-japan\u002Fliving-koudo-senmon","高度専門職ビザの実務 — ポイント制度と特権",{"articleId":593,"path":594,"title":595},"culture-matsuri","\u002Farticles\u002Fculture\u002Fmatsuri","日本の祭り — 季節と地域の象徴",{"articleId":597,"path":598,"title":599},"bj-meishi-koukan","\u002Farticles\u002Fbusiness-japanese\u002Fmeishi-koukan","名刺交換の作法 — 第一印象を決める数十秒",{"articleId":601,"path":602,"title":603},"tech-mercari-merpay-id","\u002Farticles\u002Ftech\u002Fmercari-merpay-id","メルペイのID基盤 — eKYC・本人確認の技術",{"articleId":605,"path":606,"title":607},"tech-mercari-microservices","\u002Farticles\u002Ftech\u002Fmercari-microservices-migration","Mercariのマイクロサービス移行 — モノリスから次世代へ",{"articleId":609,"path":610,"title":611},"tech-mf-multitenant","\u002Farticles\u002Ftech\u002Fmoneyforward-multitenant-saas","Money Forwardのマルチテナント設計 — データ分離とセキュリティ",{"articleId":613,"path":614,"title":615},"bj-nemawashi-ringi","\u002Farticles\u002Fbusiness-japanese\u002Fnemawashi-ringi","根回しと稟議 — 日本企業の意思決定の仕組み",{"articleId":617,"path":618,"title":619},"living-nenmatsu-chousei","\u002Farticles\u002Fliving-in-japan\u002Fnenmatsu-chousei","年末調整の仕組み — 会社員のための税精算",{"articleId":621,"path":622,"title":623},"bj-1on1","\u002Farticles\u002Fbusiness-japanese\u002Fone-on-one","1on1ミーティングの活用法 — 上司と部下の対話",{"articleId":625,"path":626,"title":627},"bj-online-kaigi","\u002Farticles\u002Fbusiness-japanese\u002Fonline-kaigi","オンライン会議のエチケット — Zoom時代のビジネスマナー",{"articleId":629,"path":630,"title":631},"culture-onsen","\u002Farticles\u002Fculture\u002Fonsen","温泉文化と入浴マナー — 名湯巡りの楽しみ方",{"articleId":633,"path":634,"title":635},"culture-pro-baseball","\u002Farticles\u002Fculture\u002Fpro-baseball","プロ野球と高校野球 — 国民的スポーツの二つの顔",{"articleId":637,"path":638,"title":639},"culture-ramen","\u002Farticles\u002Fculture\u002Framen","ラーメン地域ごとの違い — 札幌・博多・喜多方",{"articleId":641,"path":642,"title":643},"tech-recruit-data-platform","\u002Farticles\u002Ftech\u002Frecruit-data-platform","Recruit データ基盤刷新事例 — 数十サービスの統合",{"articleId":645,"path":646,"title":647},"law-roukikihou-kihon","\u002Farticles\u002Flaw\u002Froukikihou-kihon","労働基準法の基本 — 労働時間・休憩・残業規制",{"articleId":649,"path":650,"title":651},"culture-sado","\u002Farticles\u002Fculture\u002Fsado","茶道入門 — 千利休と侘び寂びの精神",{"articleId":653,"path":654,"title":655},"culture-sandou","\u002Farticles\u002Fculture\u002Fsandou","茶華書三道 — 日本の精神を体現する三つの道",{"articleId":657,"path":658,"title":659},"culture-seasonal-events","\u002Farticles\u002Fculture\u002Fseasonal-events","季節の行事 — 正月から年末まで日本の年中行事",{"articleId":661,"path":662,"title":663},"exam-sg","\u002Farticles\u002Fexams\u002Fsg","情報セキュリティマネジメント試験 — 管理者向けセキュリティ",{"articleId":665,"path":666,"title":667},"bj-shagai-mail","\u002Farticles\u002Fbusiness-japanese\u002Fshagai-mail","社外メールの書き方 — お詫び・依頼・確認",{"articleId":669,"path":670,"title":671},"bj-shanai-mail","\u002Farticles\u002Fbusiness-japanese\u002Fshanai-mail","社内メールの書き方 — 件名から結びまで",{"articleId":673,"path":674,"title":675},"culture-sumo","\u002Farticles\u002Fculture\u002Fsumo","大相撲 — 番付と力士の生活",{"articleId":677,"path":678,"title":679},"culture-sushi","\u002Farticles\u002Fculture\u002Fsushi","寿司の歴史と種類 — なれずしから江戸前まで",{"articleId":681,"path":682,"title":683},"culture-washoku","\u002Farticles\u002Fculture\u002Fwashoku","和食 — ユネスコ無形文化遺産と一汁三菜",{"articleId":685,"path":686,"title":687},"law-yuukyuu-kyuuka","\u002Farticles\u002Flaw\u002Fyuukyuu-kyuuka","有給休暇の取得ルールと最新改正",{"articleId":39,"path":689,"title":690},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fanzen-kanri","課題Ⅰ 第４編① 個人データに関する義務 ― 正確性の確保・安全管理措置・漏えい報告",{"articleId":692,"path":693,"title":694},"bill-one-auth","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fbill-one-auth","インボイス管理サービスBill Oneの認証を内製認証基盤に置き換えて認証基盤のコストを削減した話",{"articleId":696,"path":697,"title":698},"contract-one-vision","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fcontract-one-vision","契約書を\"意思決定のインフラ\"に──Contract Oneで挑む、新たな価値創造",{"articleId":700,"path":701,"title":702},"kjh-k1-h04-daisan-sha-teikyou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fdaisan-sha-teikyou","課題Ⅰ 第４編② 第三者提供の制限 ― 同意・オプトアウト・非該当類型",{"articleId":704,"path":705,"title":706},"eight-web-renewal","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Feight-web-renewal","Web版Eightのリニューアルと、安全なリリースのための取り組み",{"articleId":708,"path":709,"title":710},"kjh-k1-h04-gaikoku-kiroku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fgaikoku-kiroku","課題Ⅰ 第４編③ 外国にある第三者への提供の制限・記録義務・確認義務（法28条〜30条）",{"articleId":712,"path":713,"title":714},"kjh-k2-h04-gijutsu-jisshi","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fgijutsu-jisshi","課題Ⅱ 第４編② 技術的安全管理措置の実施項目",{"articleId":716,"path":717,"title":718},"kjh-k2-h04-gijutsu-kiso","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fgijutsu-kiso","課題Ⅱ 第４編① 技術的セキュリティ対策の基礎知識",{"articleId":720,"path":721,"title":722},"kjh-k1-h01-hotaikei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fhotaikei","課題Ⅰ 第１編 個人情報保護の法体系と各種認定制度",{"articleId":724,"path":725,"title":726},"kjh-k1-h06-hoyu-data","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fhoyu-data","課題Ⅰ 第６編 保有個人データに関する義務",{"articleId":728,"path":729,"title":730},"kjh-k1-h07-kamei-kakou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkamei-kakou","課題Ⅰ 第７編 仮名加工情報（法41条・42条）",{"articleId":732,"path":733,"title":734},"kjh-k1-h05-kanren-joho","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkanren-joho","課題Ⅰ 第５編 個人関連情報に関する義務（法31条）",{"articleId":736,"path":737,"title":738},"kjh-k1-h02-kihon-rinen","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkihon-rinen","課題Ⅰ 第２編 個人情報保護法の目的・基本理念と用語の定義",{"articleId":740,"path":741,"title":742},"kjh-k1-h09-jikkousei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h09-jikkousei","課題Ⅰ 第９編 実効性を担保する仕組み等",{"articleId":744,"path":745,"title":746},"kjh-k1-h10-gyousei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h10-gyousei","課題Ⅰ 第10編 行政機関等における個人情報等の取扱い",{"articleId":748,"path":749,"title":750},"kjh-k1-h11-my-number-hogo","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h11-my-number-hogo","課題Ⅰ 第11編② マイナンバー法 ― 特定個人情報の提供制限・保護・監督・罰則（法19条〜57条）",{"articleId":752,"path":753,"title":754},"kjh-k1-h11-my-number-sousoku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h11-my-number-sousoku","課題Ⅰ 第11編① マイナンバー法 ― 総則・個人番号・個人番号カード（法1条〜18条の5）",{"articleId":756,"path":757,"title":758},"kjh-k2-h01-guideline","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h01-guideline","課題Ⅱ 第１編② セキュリティ対策基準とガイドライン",{"articleId":760,"path":761,"title":762},"kjh-k2-h01-security-kiso","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h01-security-kiso","課題Ⅱ 第１編① 情報セキュリティの基礎と脅威",{"articleId":87,"path":764,"title":765},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h02-anzen-kanri-sochi","課題Ⅱ 第２編② 組織的・人的セキュリティ ― 安全管理措置・委託先監督・事故対応",{"articleId":11,"path":767,"title":768},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h02-soshiki-kiso","課題Ⅱ 第２編① 組織的・人的セキュリティ ― 基本方針の策定からリスク管理・規程整備まで",{"articleId":770,"path":771,"title":772},"kjh-k2-h03-office","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Foffice","課題Ⅱ 第３編 オフィスセキュリティ",{"articleId":774,"path":775,"title":776},"kjh-k1-h03-riyou-mokuteki","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Friyou-mokuteki","課題Ⅰ 第３編① 利用目的の特定・変更と利用目的による制限、不適正な利用の禁止",{"articleId":778,"path":779,"title":780},"sansan-data-intelligence","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-data-intelligence","Sansan Data Intelligenceリリースに寄せて",{"articleId":782,"path":783,"title":784},"sansan-engineer-team-infra","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-engineer-team-infra","Sansan Engineer Team：インフラ戦略部",{"articleId":786,"path":787,"title":788},"sansan-honne-15","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-honne-15","入社後のホンネ［技術本部 データ戦略部 Infrastructureグループ 渡邉 友］",{"articleId":790,"path":791,"title":792},"sansan-interview-110","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-110","SIer出身者が活躍する理由とは。Sansanを牽引するプロダクト開発に挑み続ける",{"articleId":794,"path":795,"title":796},"sansan-interview-126","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-126","AIと協働する開発組織、そして技術の深化。Sansan 新CTO笹川が語るビジョン",{"articleId":798,"path":799,"title":800},"sansan-interview-127","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-127","Sansanの技術基盤を関西から築く。新設組織で未来を創る、エンジニアの挑戦",{"articleId":802,"path":803,"title":804},"sansan-interview-130","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-130","Sansanの全社基盤を支えるPlatform Engineering Unitの挑戦",{"articleId":806,"path":807,"title":808},"sansan-interview-40","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-40","膨大な量のデータを平然と処理する。Sansanのインフラのすごさが、そこに表れている。",{"articleId":810,"path":811,"title":812},"sansan-oyaco","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-oyaco","仕事と子育ての両立を支援する制度「OYACO」",{"articleId":814,"path":815,"title":816},"kjh-k1-h03-tekisei-shutoku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Ftekisei-shutoku","課題Ⅰ 第３編② 適正な取得・要配慮個人情報・利用目的の通知",{"articleId":818,"path":819,"title":820},"kjh-k1-h08-tokumei-kakou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Ftokumei-kakou","課題Ⅰ 第８編 匿名加工情報に関する義務等（法43条〜46条）"]