[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"quiz:kjh-k2-h04-quiz":3,"quiz-article-index":341},{"quizId":4,"title":5,"titleEn":6,"topicPath":7,"questions":8},"kjh-k2-h04-quiz","第４編 情報システムセキュリティ 確認テスト","Chapter 4: Information System Security — Practice Test","software\u002Fkojin-joho-hogo\u002Fkadai-2\u002Fhen-04-jouhou-system",[9,39,63,86,110,135,159,183,205,228,248,273,297,321],{"id":10,"articleId":11,"question":12,"options":15,"correctLabel":25,"explanation":32,"tags":35},"kjh-k2-h04-q01","kjh-k2-h04-gijutsu-kiso",{"en":13,"jp":14},"Which of the following correctly compares shared-key (symmetric) encryption and public-key (asymmetric) encryption?","[共通鍵]{きょうつうかぎ:shared key}[暗号]{あんごう:encryption}[方式]{ほうしき:method}と[公開鍵]{こうかいかぎ:public key}[暗号]{あんごう:encryption}[方式]{ほうしき:method}の[比較]{ひかく:comparison}として[正]{ただ:correct}しいものはどれか。",[16,20,24,28],{"label":17,"jp":18,"en":19},"ア","[共通鍵]{きょうつうかぎ:shared key}[暗号]{あんごう:encryption}は[処理]{しょり:processing}[速度]{そくど:speed}が[遅]{おそ:slow}いが、[鍵]{かぎ:key}[配送]{はいそう:distribution}[問題]{もんだい:problem}がない","Shared-key encryption is slow but has no key distribution problem",{"label":21,"jp":22,"en":23},"イ","[公開鍵]{こうかいかぎ:public key}[暗号]{あんごう:encryption}は[処理]{しょり:processing}[速度]{そくど:speed}が[速]{はや:fast}いが、[鍵]{かぎ:key}[配送]{はいそう:distribution}[問題]{もんだい:problem}がある","Public-key encryption is fast but has a key distribution problem",{"label":25,"jp":26,"en":27},"ウ","[共通鍵]{きょうつうかぎ:shared key}[暗号]{あんごう:encryption}は[処理]{しょり:processing}[速度]{そくど:speed}が[速]{はや:fast}いが、[鍵]{かぎ:key}[配送]{はいそう:distribution}[問題]{もんだい:problem}がある","Shared-key encryption is fast but has a key distribution problem",{"label":29,"jp":30,"en":31},"エ","[両者]{りょうしゃ:both}とも[同]{おな:same}じ[鍵]{かぎ:key}を[使]{つか:use}って[暗号化]{あんごうか:encryption}・[復号]{ふくごう:decryption}を[行]{おこな:perform}う","Both use the same key for encryption and decryption",{"en":33,"jp":34},"Shared-key encryption (e.g., AES) is fast but requires both parties to share the same key, creating a key distribution problem. Public-key encryption (e.g., RSA) solves the distribution problem but is slower. Options A and B have the characteristics reversed. Option D only describes shared-key encryption.","[共通鍵]{きょうつうかぎ:shared key}[暗号]{あんごう:encryption}（AES[等]{とう:etc.}）は[処理]{しょり:processing}が[高速]{こうそく:high speed}だが、[送信者]{そうしんしゃ:sender}と[受信者]{じゅしんしゃ:receiver}で[同]{おな:same}じ[鍵]{かぎ:key}を[共有]{きょうゆう:share}する[必要]{ひつよう:need}があり、[鍵]{かぎ:key}[配送]{はいそう:distribution}[問題]{もんだい:problem}が[生]{しょう:arise}じる。[公開鍵]{こうかいかぎ:public key}[暗号]{あんごう:encryption}（RSA[等]{とう:etc.}）は[鍵]{かぎ:key}[配送]{はいそう:distribution}[問題]{もんだい:problem}を[解決]{かいけつ:solve}するが[処理]{しょり:processing}が[遅]{おそ:slow}い。ア・イは[特徴]{とくちょう:characteristic}が[逆]{ぎゃく:reverse}。エは[共通鍵]{きょうつうかぎ:shared key}のみの[説明]{せつめい:explanation}。",[36,37,38],"encryption","symmetric","asymmetric",{"id":40,"articleId":11,"question":41,"options":44,"correctLabel":21,"explanation":57,"tags":60},"kjh-k2-h04-q02",{"en":42,"jp":43},"Which of the following correctly explains multi-factor authentication?","[多]{た:multi}[要素]{ようそ:factor}[認証]{にんしょう:authentication}の[説明]{せつめい:explanation}として[正]{ただ:correct}しいものはどれか。",[45,48,51,54],{"label":17,"jp":46,"en":47},"パスワードを2[回]{かい:times}[入力]{にゅうりょく:input}させること","Requiring a password to be entered twice",{"label":21,"jp":49,"en":50},"[知識]{ちしき:knowledge}・[所持]{しょじ:possession}・[生体]{せいたい:biometric}[情報]{じょうほう:information}のうち、2つ[以上]{いじょう:or more}の[異]{こと:different}なる[要素]{ようそ:factor}を[組]{く:combine}み[合]{あ:combine}わせた[認証]{にんしょう:authentication}","Authentication combining two or more different factors from knowledge, possession, and biometrics",{"label":25,"jp":52,"en":53},"IDとパスワードに[加]{くわ:add}え、[秘密]{ひみつ:secret}の[質問]{しつもん:question}を[使]{つか:use}う[認証]{にんしょう:authentication}","Authentication using an ID, password, and a secret question",{"label":29,"jp":55,"en":56},"[複数]{ふくすう:multiple}のパスワードを[使]{つか:use}い[分]{わ:separate}けること","Using multiple different passwords",{"en":58,"jp":59},"Multi-factor authentication combines 2 or more of the 3 factors: knowledge (passwords etc.), possession (smartphones, IC cards etc.), and biometrics (fingerprints etc.). Option A repeats the same factor. Option C combines password and secret question — both are \"knowledge\" factors, so it is not multi-factor. Option D also repeats the same factor type.","[多]{た:multi}[要素]{ようそ:factor}[認証]{にんしょう:authentication}は「[知識]{ちしき:knowledge}（パスワード[等]{とう:etc.}）」「[所持]{しょじ:possession}（スマートフォン・ICカード[等]{とう:etc.}）」「[生体]{せいたい:biometric}[情報]{じょうほう:information}（[指紋]{しもん:fingerprint}[等]{とう:etc.}）」の3[要素]{ようそ:factors}のうち2つ[以上]{いじょう:or more}を[組]{く:combine}み[合]{あ:combine}わせる。アはパスワードの2[回]{かい:times}[入力]{にゅうりょく:input}で[同]{おな:same}じ[要素]{ようそ:factor}。ウは[秘密]{ひみつ:secret}の[質問]{しつもん:question}もパスワードも「[知識]{ちしき:knowledge}」[要素]{ようそ:factor}なので[多]{た:multi}[要素]{ようそ:factor}ではない。エも[同]{おな:same}じ[要素]{ようそ:factor}の[繰]{く:repeat}り[返]{かえ:return}し。",[61,62],"authentication","MFA",{"id":64,"articleId":11,"question":65,"options":68,"correctLabel":25,"explanation":81,"tags":84},"kjh-k2-h04-q03",{"en":66,"jp":67},"Which type of firewall inspects packet contents at the application layer?","ファイアウォールの[種類]{しゅるい:types}のうち、アプリケーション[層]{そう:layer}でパケットの[内容]{ないよう:content}を[検査]{けんさ:inspect}するものはどれか。",[69,72,75,78],{"label":17,"jp":70,"en":71},"パケットフィルタリング","Packet filtering",{"label":21,"jp":73,"en":74},"ステートフルインスペクション","Stateful inspection",{"label":25,"jp":76,"en":77},"アプリケーションゲートウェイ（プロキシ[型]{がた:type}）","Application gateway (proxy type)",{"label":29,"jp":79,"en":80},"NAT（ネットワークアドレス[変換]{へんかん:translation}）","NAT (Network Address Translation)",{"en":82,"jp":83},"An application gateway (proxy type) inspects communication content at the application layer for detailed control. Packet filtering controls by IP address and port number. Stateful inspection manages communication state for decision-making. NAT is an address translation technology, not a type of firewall.","アプリケーションゲートウェイ（プロキシ[型]{がた:type}）はアプリケーション[層]{そう:layer}で[通信]{つうしん:communication}[内容]{ないよう:content}を[検査]{けんさ:inspect}し、[詳細]{しょうさい:detailed}な[制御]{せいぎょ:control}が[可能]{かのう:possible}。パケットフィルタリングはIPアドレスやポート[番号]{ばんごう:number}で[制御]{せいぎょ:control}する[方式]{ほうしき:method}。ステートフルインスペクションは[通信]{つうしん:communication}の[状態]{じょうたい:state}を[管理]{かんり:manage}して[判断]{はんだん:judge}する[方式]{ほうしき:method}。NATはアドレス[変換]{へんかん:translation}[技術]{ぎじゅつ:technology}でありファイアウォールの[種類]{しゅるい:type}ではない。",[85],"firewall",{"id":87,"articleId":11,"question":88,"options":91,"correctLabel":21,"explanation":104,"tags":107},"kjh-k2-h04-q04",{"en":89,"jp":90},"Which of the following correctly describes the difference between IDS (Intrusion Detection System) and IPS (Intrusion Prevention System)?","IDS（[侵入]{しんにゅう:intrusion}[検知]{けんち:detection}システム）とIPS（[侵入]{しんにゅう:intrusion}[防止]{ぼうし:prevention}システム）の[違]{ちが:difference}いとして[正]{ただ:correct}しいものはどれか。",[92,95,98,101],{"label":17,"jp":93,"en":94},"IDSは[不正]{ふせい:unauthorized}アクセスを[検知]{けんち:detect}し[自動]{じどう:automatically}[遮断]{しゃだん:block}する。IPSは[検知]{けんち:detect}のみ[行]{おこな:perform}う","IDS detects and automatically blocks unauthorized access. IPS only detects",{"label":21,"jp":96,"en":97},"IDSは[不正]{ふせい:unauthorized}アクセスの[検知]{けんち:detection}・[通知]{つうち:notification}を[行]{おこな:perform}い、IPSは[検知]{けんち:detection}に[加]{くわ:add}え[自動]{じどう:automatically}[遮断]{しゃだん:block}まで[行]{おこな:perform}う","IDS detects and notifies of unauthorized access; IPS detects and also automatically blocks it",{"label":25,"jp":99,"en":100},"[両者]{りょうしゃ:both}とも[検知]{けんち:detection}のみで[遮断]{しゃだん:blocking}[機能]{きのう:function}はない","Both only detect and have no blocking function",{"label":29,"jp":102,"en":103},"IPSはファイアウォールの[別名]{べつめい:alias}である","IPS is another name for a firewall",{"en":105,"jp":106},"IDS detects unauthorized communication and notifies the administrator (detection only). IPS also automatically blocks the relevant traffic. Option A is reversed. Option C ignores the blocking function of IPS. Option D is wrong — IPS and firewalls are separate mechanisms.","IDSは[不正]{ふせい:unauthorized}な[通信]{つうしん:communication}を[検知]{けんち:detect}して[管理者]{かんりしゃ:administrator}に[通知]{つうち:notify}する（[検知]{けんち:detection}のみ）。IPSは[検知]{けんち:detection}に[加]{くわ:add}えて[該当]{がいとう:relevant}[通信]{つうしん:communication}を[自動的]{じどうてき:automatically}に[遮断]{しゃだん:block}する。アは[逆]{ぎゃく:reverse}。ウはIPSの[遮断]{しゃだん:blocking}[機能]{きのう:function}を[無視]{むし:ignore}している。エはIPSとファイアウォールは[別]{べつ:separate}の[仕組]{しくみ:mechanism}み。",[108,109],"IDS","IPS",{"id":111,"articleId":112,"question":113,"options":116,"correctLabel":17,"explanation":129,"tags":132},"kjh-k2-h04-q05","kjh-k2-h04-gijutsu-jisshi",{"en":114,"jp":115},"Which of the following best describes the main function of SIEM (Security Information and Event Management)?","SIEM（Security Information and Event Management）の[主]{おも:main}な[機能]{きのう:function}として[最]{もっと:most}も[適切]{てきせつ:appropriate}なものはどれか。",[117,120,123,126],{"label":17,"jp":118,"en":119},"[各種]{かくしゅ:various}ログを[一元的]{いちげんてき:centrally}に[収集]{しゅうしゅう:collect}・[分析]{ぶんせき:analyze}し、セキュリティ[脅威]{きょうい:threat}を[可視化]{かしか:visualize}する","Centrally collecting and analyzing various logs to visualize security threats",{"label":21,"jp":121,"en":122},"ウイルスを[検知]{けんち:detect}・[駆除]{くじょ:remove}する","Detecting and removing viruses",{"label":25,"jp":124,"en":125},"ネットワーク[通信]{つうしん:communication}を[暗号化]{あんごうか:encrypt}する","Encrypting network communication",{"label":29,"jp":127,"en":128},"[外部]{がいぶ:external}からの[不正]{ふせい:unauthorized}アクセスを[遮断]{しゃだん:block}する","Blocking unauthorized access from outside",{"en":130,"jp":131},"SIEM is a tool that centrally collects and correlates logs from firewalls, IDS\u002FIPS, servers, etc. to support early detection of security incidents. Option B describes antivirus software, C describes VPN functionality, and D describes firewall\u002FIPS functionality.","SIEMはファイアウォール、IDS\u002FIPS、サーバ[等]{とう:etc.}の[各種]{かくしゅ:various}ログを[一元的]{いちげんてき:centrally}に[収集]{しゅうしゅう:collect}・[相関]{そうかん:correlate}[分析]{ぶんせき:analyze}し、セキュリティインシデントの[早期]{そうき:early}[発見]{はっけん:discovery}を[支援]{しえん:support}するツール。イはアンチウイルスソフト、ウはVPN[等]{とう:etc.}の[機能]{きのう:function}、エはファイアウォールやIPSの[機能]{きのう:function}。",[133,134],"SIEM","log-management",{"id":136,"articleId":112,"question":137,"options":140,"correctLabel":25,"explanation":153,"tags":156},"kjh-k2-h04-q06",{"en":138,"jp":139},"Which of the following correctly explains the shared responsibility model in cloud services?","クラウドサービスにおける[責任]{せきにん:responsibility}[共有]{きょうゆう:shared}モデルの[説明]{せつめい:explanation}として[正]{ただ:correct}しいものはどれか。",[141,144,147,150],{"label":17,"jp":142,"en":143},"セキュリティの[全]{すべ:all}ての[責任]{せきにん:responsibility}はクラウド[事業者]{じぎょうしゃ:provider}にある","All security responsibility lies with the cloud provider",{"label":21,"jp":145,"en":146},"セキュリティの[全]{すべ:all}ての[責任]{せきにん:responsibility}は[利用者]{りようしゃ:user}にある","All security responsibility lies with the user",{"label":25,"jp":148,"en":149},"クラウド[事業者]{じぎょうしゃ:provider}はインフラ[部分]{ぶぶん:portion}、[利用者]{りようしゃ:user}はデータやアクセス[管理]{かんり:management}[等]{とう:etc.}をそれぞれ[分担]{ぶんたん:share}する","The cloud provider is responsible for the infrastructure portion, while the user is responsible for data and access management, etc.",{"label":29,"jp":151,"en":152},"IaaSではアプリケーションの[管理]{かんり:management}もクラウド[事業者]{じぎょうしゃ:provider}の[責任]{せきにん:responsibility}である","In IaaS, application management is also the cloud provider's responsibility",{"en":154,"jp":155},"Under the shared responsibility model, the cloud provider handles infrastructure (network, physical servers, etc.) and the user handles data, access management, applications, etc. Options A and B incorrectly place all responsibility on one party. Option D is wrong because in IaaS, the user must manage OS and applications.","[責任]{せきにん:responsibility}[共有]{きょうゆう:shared}モデルでは、クラウド[事業者]{じぎょうしゃ:provider}がインフラ（ネットワーク・[物理]{ぶつり:physical}サーバ[等]{とう:etc.}）を、[利用者]{りようしゃ:user}がデータ・アクセス[管理]{かんり:management}・アプリケーション[等]{とう:etc.}を[分担]{ぶんたん:share}する。ア・イのように[片方]{かたほう:one side}だけに[全]{すべ:all}[責任]{せきにん:responsibility}があるわけではない。エはIaaSでは[利用者]{りようしゃ:user}がOS・アプリケーションまで[管理]{かんり:manage}する[必要]{ひつよう:need}がある。",[157,158],"cloud","shared-responsibility",{"id":160,"articleId":112,"question":161,"options":164,"correctLabel":25,"explanation":177,"tags":180},"kjh-k2-h04-q07",{"en":162,"jp":163},"Among antivirus detection methods, which monitors operations during execution to detect suspicious behavior?","アンチウイルスソフトの[検知]{けんち:detection}[方式]{ほうしき:methods}のうち、[実行]{じっこう:execution}[時]{じ:time}の[動作]{どうさ:behavior}を[監視]{かんし:monitor}して[不審]{ふしん:suspicious}な[挙動]{きょどう:activities}を[検知]{けんち:detect}する[方式]{ほうしき:method}はどれか。",[165,168,171,174],{"label":17,"jp":166,"en":167},"パターンマッチング","Pattern matching",{"label":21,"jp":169,"en":170},"ヒューリスティック[検知]{けんち:detection}","Heuristic detection",{"label":25,"jp":172,"en":173},"ビヘイビア（[振る舞い]{ふるまい:behavior}）[分析]{ぶんせき:analysis}","Behavior analysis",{"label":29,"jp":175,"en":176},"[定義]{ていぎ:definition}ファイル[更新]{こうしん:update}","Definition file update",{"en":178,"jp":179},"Behavior analysis monitors operations during execution to detect suspicious behavior. Pattern matching compares against definition files of known malware. Heuristic detection estimates unknown malware from structural characteristics. Option D is operational task, not a detection method. Combining the three methods enhances detection rate.","ビヘイビア（[振る舞い]{ふるまい:behavior}）[分析]{ぶんせき:analysis}は[実行]{じっこう:execution}[時]{じ:time}の[動作]{どうさ:operation}を[監視]{かんし:monitor}し[不審]{ふしん:suspicious}な[挙動]{きょどう:behavior}を[検知]{けんち:detect}する。パターンマッチングは[既知]{きち:known}マルウェアの[特徴]{とくちょう:characteristic}[定義]{ていぎ:definition}ファイルとの[照合]{しょうごう:comparison}、ヒューリスティック[検知]{けんち:detection}は[構造的]{こうぞうてき:structural}[特徴]{とくちょう:characteristics}から[未知]{みち:unknown}マルウェアを[推定]{すいてい:estimate}する[方式]{ほうしき:method}。エは[検知]{けんち:detection}[方式]{ほうしき:method}ではなく[運用]{うんよう:operational}[作業]{さぎょう:task}。3[方式]{ほうしき:methods}を[組]{く:combine}み[合]{あ:combine}わせて[検知]{けんち:detection}[率]{りつ:rate}を[高]{たか:enhance}める。",[181,182],"antivirus","behavior-analysis",{"id":184,"articleId":112,"question":185,"options":188,"correctLabel":17,"explanation":199,"tags":202},"kjh-k2-h04-q08",{"en":186,"jp":187},"Which is the representative Japanese information source for collecting vulnerability information?","[脆弱性]{ぜいじゃくせい:vulnerability}[情報]{じょうほう:information}を[収集]{しゅうしゅう:collect}する[際]{さい:when}に[参照]{さんしょう:refer}される[情報]{じょうほう:information}[源]{げん:source}として[日本]{にほん:Japan}の[代表]{だいひょう:representative}[的]{てき:-ical}なものはどれか。",[189,192,195,197],{"label":17,"jp":190,"en":191},"JVN（Japan Vulnerability Notes）","JVN (Japan Vulnerability Notes)",{"label":21,"jp":193,"en":194},"CVSS（Common Vulnerability Scoring System）","CVSS (Common Vulnerability Scoring System)",{"label":25,"jp":196,"en":196},"NIST CSF",{"label":29,"jp":198,"en":198},"ISO\u002FIEC 27017",{"en":200,"jp":201},"JVN (Japan Vulnerability Notes) is the Japanese vulnerability information portal jointly operated by IPA and JPCERT\u002FCC. Internationally, CVE (Common Vulnerabilities and Exposures) is used. CVSS is a severity evaluation standard; NIST CSF is the Cybersecurity Framework; ISO\u002FIEC 27017 is a cloud security standard.","JVN（Japan Vulnerability Notes）はIPAとJPCERT\u002FCCが[共同]{きょうどう:jointly}[運営]{うんえい:operate}する[日本]{にほん:Japan}の[脆弱性]{ぜいじゃくせい:vulnerability}[情報]{じょうほう:information}ポータル。[国際]{こくさい:international}[的]{てき:-ically}にはCVE（Common Vulnerabilities and Exposures）が[利用]{りよう:used}される。CVSSは[脆弱性]{ぜいじゃくせい:vulnerability}の[深刻度]{しんこくど:severity}を[評価]{ひょうか:evaluate}する[基準]{きじゅん:standard}、NIST CSFはサイバーセキュリティフレームワーク、ISO\u002FIEC 27017はクラウド[セキュリティ]{セキュリティ:security}[規格]{きかく:standard}。",[203,204],"vulnerability-management","JVN",{"id":206,"articleId":112,"question":207,"options":210,"correctLabel":21,"explanation":222,"tags":225},"kjh-k2-h04-q09",{"en":208,"jp":209},"Which best describes the primary role of WAF (Web Application Firewall)?","WAF（Web Application Firewall）の[主]{おも:primary}な[役割]{やくわり:role}として[最]{もっと:most}も[適切]{てきせつ:appropriate}なものはどれか。",[211,214,217,219],{"label":17,"jp":212,"en":213},"IPアドレスやポート[番号]{ばんごう:number}でパケットを[制御]{せいぎょ:control}する","Control packets by IP address and port number",{"label":21,"jp":215,"en":216},"SQLインジェクションやクロスサイトスクリプティングなどWebアプリケーション[層]{そう:layer}の[攻撃]{こうげき:attacks}から[防御]{ぼうぎょ:defend}する","Defend against web application layer attacks such as SQL injection and cross-site scripting",{"label":25,"jp":121,"en":218},"Detect and remove viruses",{"label":29,"jp":220,"en":221},"[利用者]{りようしゃ:user}の[認証]{にんしょう:authentication}[情報]{じょうほう:information}を[管理]{かんり:manage}する","Manage user authentication information",{"en":223,"jp":224},"WAF is a dedicated firewall that detects and defends against attacks on web applications at the application layer (OSI Layer 7) — SQL injection, XSS, CSRF, etc. Option A is an ordinary packet-filtering firewall, C is antivirus, and D is an identity management system.","WAFはアプリケーション[層]{そう:layer}（OSI[第]{だい:Layer}7[層]{そう:layer}）でWebアプリケーションへの[攻撃]{こうげき:attacks}（SQLインジェクション、XSS、CSRF[等]{とう:etc.}）を[検知]{けんち:detect}・[防御]{ぼうぎょ:defend}する[専用]{せんよう:dedicated}ファイアウォール。アは[通常]{つうじょう:ordinary}のパケットフィルタリング[型]{がた:type}ファイアウォール、ウはアンチウイルス、エはID[管理]{かんり:management}システムの[役割]{やくわり:role}である。",[226,227],"WAF","web-application",{"id":229,"articleId":112,"question":230,"options":233,"correctLabel":29,"explanation":243,"tags":246},"kjh-k2-h04-q10",{"en":231,"jp":232},"Which is the correct minimum version of encryption protocol that should be used when transmitting\u002Freceiving personal data?","[個人]{こじん:personal}データを[送受信]{そうじゅしん:transmit and receive}する[際]{さい:when}に[使用]{しよう:use}すべき[暗号]{あんごう:encryption}[プロトコル]{プロトコル:protocol}の[最低]{さいてい:minimum}[バージョン]{バージョン:version}として[正]{ただ:correct}しいものはどれか。",[234,236,238,240],{"label":17,"jp":235,"en":235},"SSL 3.0",{"label":21,"jp":237,"en":237},"TLS 1.0",{"label":25,"jp":239,"en":239},"TLS 1.1",{"label":29,"jp":241,"en":242},"TLS 1.2 [以上]{いじょう:or higher}","TLS 1.2 or higher",{"en":244,"jp":245},"TLS 1.2 or higher should be used for transmitting personal data. SSL 3.0 and TLS 1.0\u002F1.1 are already deprecated and have known vulnerabilities — their use should be ceased. For connections from outside the company, VPN is used together to protect the communication route.","[個人]{こじん:personal}データの[送受信]{そうじゅしん:transmission}にはTLS 1.2[以上]{いじょう:or higher}を[使用]{しよう:use}する。SSL 3.0・TLS 1.0\u002F1.1は[既]{すで:already}に[非推奨]{ひすいしょう:deprecated}で[既知]{きち:known}の[脆弱性]{ぜいじゃくせい:vulnerabilities}が[存在]{そんざい:exist}するため[使用]{しよう:use}を[停止]{ていし:cease}すべき。[社外]{しゃがい:outside the company}からの[接続]{せつぞく:connection}にはVPNを[併用]{へいよう:use together}して[通信]{つうしん:communication}[経路]{けいろ:route}を[保護]{ほご:protect}する。",[247,36],"TLS",{"id":249,"articleId":11,"question":250,"options":253,"correctLabel":25,"explanation":266,"tags":269},"kjh-k2-h04-q11",{"en":251,"jp":252},"Which is correct about types of VPN?","VPNの[種類]{しゅるい:types}に[関]{かん:related}する[説明]{せつめい:description}として[正]{ただ:correct}しいものはどれか。",[254,257,260,263],{"label":17,"jp":255,"en":256},"IPsec VPNはOSI[第]{だい:Layer}7[層]{そう:layer}で[動作]{どうさ:operate}し、ウェブブラウザのみで[利用]{りよう:use}できる","IPsec VPN operates at OSI Layer 7 and works only with a web browser",{"label":21,"jp":258,"en":259},"SSL-VPNはOSI[第]{だい:Layer}3[層]{そう:layer}で[動作]{どうさ:operate}し、[拠点]{きょてん:base}[間]{かん:between}[接続]{せつぞく:connection}に[適]{てき:suitable}する","SSL-VPN operates at OSI Layer 3 and is suitable for site-to-site connections",{"label":25,"jp":261,"en":262},"IPsec VPNはOSI[第]{だい:Layer}3[層]{そう:layer}で[動作]{どうさ:operate}し[拠点]{きょてん:base}[間]{かん:between}（site-to-site）[接続]{せつぞく:connection}に[適]{てき:suitable}し、SSL-VPNは[第]{だい:Layer}4〜7[層]{そう:layer}で[動作]{どうさ:operate}しリモートアクセスに[広く]{ひろく:widely}[普及]{ふきゅう:used}している","IPsec VPN operates at OSI Layer 3 and suits site-to-site connections; SSL-VPN operates at Layers 4-7 and is widely used for remote access",{"label":29,"jp":264,"en":265},"[両者]{りょうしゃ:both}とも[暗号化]{あんごうか:encryption}[機能]{きのう:function}を[持]{も:have}たない","Neither has encryption functionality",{"en":267,"jp":268},"IPsec VPN operates at OSI Layer 3 (network) and is suitable for site-to-site connections. SSL-VPN operates at Layers 4-7 and is widely used for remote access since it works with just a web browser. Both construct an encrypted communication path over public networks.","IPsec VPNはOSI[第]{だい:Layer}3[層]{そう:layer}（ネットワーク[層]{そう:layer}）で[動作]{どうさ:operates}し、[拠点]{きょてん:site}[間]{かん:between}[接続]{せつぞく:connection}（site-to-site）に[適]{てき:suitable}する。SSL-VPNは[第]{だい:Layer}4〜7[層]{そう:layer}で[動作]{どうさ:operates}し、ウェブブラウザだけで[利用]{りよう:use}できるためリモートアクセスに[広く]{ひろく:widely}[普及]{ふきゅう:used}。[両者]{りょうしゃ:both}とも[公衆]{こうしゅう:public}ネットワーク[上]{じょう:on}に[暗号化]{あんごうか:encrypted}[通信]{つうしん:communication}[経路]{けいろ:path}を[構築]{こうちく:construct}する。",[270,271,272],"VPN","IPsec","SSL-VPN",{"id":274,"articleId":112,"question":275,"options":278,"correctLabel":17,"explanation":291,"tags":294},"kjh-k2-h04-q12",{"en":276,"jp":277},"Which best describes EDR (Endpoint Detection and Response)?","EDR（Endpoint Detection and Response）の[特徴]{とくちょう:characteristic}として[最]{もっと:most}も[適切]{てきせつ:appropriate}なものはどれか。",[279,282,285,288],{"label":17,"jp":280,"en":281},"[端末]{たんまつ:endpoint}での[挙動]{きょどう:behavior}を[継続]{けいぞく:continuously}[的]{てき:-ly}に[監視]{かんし:monitor}し、インシデント[発生]{はっせい:occurrence}[時]{じ:time}の[検知]{けんち:detection}・[調査]{ちょうさ:investigation}・[対応]{たいおう:response}を[支援]{しえん:support}する","Continuously monitors endpoint behavior to support detection, investigation, and response when incidents occur",{"label":21,"jp":283,"en":284},"ネットワーク[境界]{きょうかい:boundary}でパケットを[検査]{けんさ:inspect}する","Inspects packets at the network boundary",{"label":25,"jp":286,"en":287},"[既知]{きち:known}マルウェアを[定義]{ていぎ:definition}ファイルとの[照合]{しょうごう:comparison}で[検知]{けんち:detect}するのみ","Only detects known malware via comparison with definition files",{"label":29,"jp":289,"en":290},"クラウドサービスの[暗号化]{あんごうか:encryption}[鍵]{かぎ:key}を[管理]{かんり:manage}する","Manages encryption keys for cloud services",{"en":292,"jp":293},"EDR complements conventional antivirus, continuously recording and monitoring endpoint (PC, server) behavior to support early detection, root cause investigation, and containment when incidents occur. A characteristic feature is the ability to handle unknown attacks.","EDRは[従来]{じゅうらい:conventional}のアンチウイルスを[補完]{ほかん:complement}し、[端末]{たんまつ:endpoint}（PC・サーバ）での[挙動]{きょどう:behavior}を[継続]{けいぞく:continuously}[的]{てき:-ly}に[記録]{きろく:record}・[監視]{かんし:monitor}し、インシデント[発生]{はっせい:occurrence}[時]{じ:time}の[早期]{そうき:early}[検知]{けんち:detection}・[原因]{げんいん:cause}[調査]{ちょうさ:investigation}・[封じ込め]{ふうじこめ:containment}を[支援]{しえん:support}する[仕組み]{しくみ:mechanism}。[未知]{みち:unknown}[攻撃]{こうげき:attacks}にも[対応]{たいおう:respond}できる[点]{てん:point}が[特徴]{とくちょう:characteristic}。",[295,296],"EDR","endpoint",{"id":298,"articleId":11,"question":299,"options":302,"correctLabel":21,"explanation":315,"tags":318},"kjh-k2-h04-q13",{"en":300,"jp":301},"Which is correct about digital signatures?","デジタル[署名]{しょめい:signature}に[関]{かん:related}する[説明]{せつめい:explanation}として[正]{ただ:correct}しいものはどれか。",[303,306,309,312],{"label":17,"jp":304,"en":305},"[送信者]{そうしんしゃ:sender}が[自]{みずか:own}らの[公開鍵]{こうかいかぎ:public key}でハッシュ[値]{ち:value}を[暗号化]{あんごうか:encrypt}する","The sender encrypts the hash value with their own public key",{"label":21,"jp":307,"en":308},"[送信者]{そうしんしゃ:sender}が[自]{みずか:own}らの[秘密鍵]{ひみつかぎ:private key}でハッシュ[値]{ち:value}を[暗号化]{あんごうか:encrypt}し、[受信者]{じゅしんしゃ:recipient}が[送信者]{そうしんしゃ:sender}の[公開鍵]{こうかいかぎ:public key}で[検証]{けんしょう:verify}する","The sender encrypts the hash value with their private key, and the recipient verifies with the sender's public key",{"label":25,"jp":310,"en":311},"[共通鍵]{きょうつうかぎ:shared key}で[文書]{ぶんしょ:document}[全体]{ぜんたい:entire}を[暗号化]{あんごうか:encrypt}する","Encrypts the entire document with a shared key",{"label":29,"jp":313,"en":314},"デジタル[署名]{しょめい:signature}は[機密性]{きみつせい:confidentiality}を[確保]{かくほ:ensure}する[技術]{ぎじゅつ:technology}である","Digital signatures are a technology for ensuring confidentiality",{"en":316,"jp":317},"A digital signature works by the sender encrypting the document's hash value with their own private key, and the recipient verifying with the sender's public key. This ensures integrity (tamper detection) and non-repudiation. It is not for confidentiality (encryption) purposes.","デジタル[署名]{しょめい:signature}は[送信者]{そうしんしゃ:sender}が[文書]{ぶんしょ:document}のハッシュ[値]{ち:value}を[自]{みずか:own}らの[秘密鍵]{ひみつかぎ:private key}で[暗号化]{あんごうか:encrypt}し、[受信者]{じゅしんしゃ:recipient}が[送信者]{そうしんしゃ:sender}の[公開鍵]{こうかいかぎ:public key}で[検証]{けんしょう:verify}する[仕組み]{しくみ:mechanism}。これにより[完全性]{かんぜんせい:integrity}（[改ざん]{かいざん:tamper}[検出]{けんしゅつ:detection}）と[否認]{ひにん:non-}[防止]{ぼうし:repudiation}を[確保]{かくほ:ensure}する。[機密性]{きみつせい:confidentiality}（[暗号化]{あんごうか:encryption}）[目的]{もくてき:purpose}ではない。",[319,320],"digital-signature","PKI",{"id":322,"articleId":112,"question":323,"options":326,"correctLabel":25,"explanation":335,"tags":338},"kjh-k2-h04-q14",{"en":324,"jp":325},"Which international standard for cloud security is a reference when outsourcing personal data handling to a cloud provider?","[個人]{こじん:personal}データを[扱]{あつか:handle}う[業務]{ぎょうむ:business}をクラウド[事業者]{じぎょうしゃ:provider}に[委託]{いたく:outsource}する[際]{さい:when}に[参考]{さんこう:reference}となるクラウドセキュリティの[国際]{こくさい:international}[規格]{きかく:standard}はどれか。",[327,329,331,333],{"label":17,"jp":328,"en":328},"ISO\u002FIEC 27001",{"label":21,"jp":330,"en":330},"ISO\u002FIEC 27002",{"label":25,"jp":332,"en":332},"ISO\u002FIEC 27017 \u002F 27018",{"label":29,"jp":334,"en":334},"ISO\u002FIEC 9001",{"en":336,"jp":337},"ISO\u002FIEC 27017 is a cloud security control guideline; ISO\u002FIEC 27018 is the standard for protecting personal information (PII) in the cloud. When outsourcing, fulfill the outsourcing partner supervision obligation under Article 28 of the amended Act and reference these standards. 27001 is ISMS requirements, 27002 is a code of practice for controls, and 9001 is quality management.","ISO\u002FIEC 27017はクラウドセキュリティの[管理策]{かんりさく:controls}[指針]{ししん:guidelines}、ISO\u002FIEC 27018はクラウド[上]{じょう:on}の[個人]{こじん:personal}[情報]{じょうほう:information}（PII）[保護]{ほご:protection}[規格]{きかく:standard}。[委託]{いたく:outsourcing}[時]{じ:time}は[改正]{かいせい:amended}[法]{ほう:Act}[第]{だい:Article}28[条]{じょう:article}に[基]{もと:based}づく[委託先]{いたくさき:outsourcing partner}[監督]{かんとく:supervision}[義務]{ぎむ:obligation}を[果]{は:fulfill}たし、これら[規格]{きかく:standards}を[参照]{さんしょう:reference}する。27001はISMS[要求]{ようきゅう:requirements}、27002は[管理策]{かんりさく:controls}[実践]{じっせん:practice}[規範]{きはん:code}、9001は[品質]{ひんしつ:quality}[管理]{かんり:management}システム。",[157,339,340],"ISO27017","ISO27018",{"culture-anime-studio-ghibli":342,"culture-bonsai-art":346,"tech-cybozu-kintone-no-code":350,"living-denki-gas-suidou":354,"tech-gree-mobile-game-ops":358,"culture-green-tea-types":362,"living-gym-fitness":366,"living-internet-hikari":370,"living-jisha-de-kau":374,"exam-jlpt-n3-grammar":378,"exam-jlpt-n3-vocab":382,"bj-job-gata-koyou":386,"culture-kabuki-noh-bunraku":390,"bj-karoushi-hatarakikata":394,"living-keitai-mobile-plan":398,"living-konbini-atm-banking":402,"living-kosodate-hoiku":406,"culture-nihon-teien":410,"bj-nomikai-survival":414,"tech-pixiv-image-cdn":418,"culture-sake-shochu":422,"bj-sankyu-ikukyu":426,"tech-sansan-eight-platform":430,"culture-shichi-go-san":434,"bj-shukatsu-shinsotsu":438,"tech-smartnews-recommendation":442,"bj-taishoku-todoke":446,"bj-telework-policy":450,"bj-tenshoku-resume":454,"tech-yahoo-japan-search":458,"culture-anime-business":462,"exam-ap":466,"exam-aws-japan":470,"law-chosakuken":474,"tech-cookpad-recipe-search":478,"tech-cybozu-kintone-api":482,"tech-dena-observability":486,"law-denshi-chouho":490,"tech-digital-cho-cloud":494,"exam-fe":498,"tech-freee-accounting":502,"law-furiransu-hou":506,"law-harassment":510,"tech-hatena-mackerel":514,"bj-hourensou":518,"bj-hyouka-mendan":522,"law-invoice":526,"exam-it-passport":530,"culture-izakaya":534,"culture-j-league":538,"culture-jinja-tera":542,"exam-jlpt-n1-dokkai":546,"exam-jlpt-n2-business":550,"bj-kaigi-manner":554,"living-kakutei-shinkoku":558,"bj-keigo-kihon":562,"law-keihin-hyouji":566,"living-kenkou-hoken":570,"living-kosei-nenkin":574,"tech-line-llmops":578,"tech-line-streaming":582,"living-chintai-keiyaku":586,"living-eijuken":590,"living-engineer-visa":594,"living-ginkou-koza":598,"living-hikkoshi-checklist":602,"living-koudo-senmon":606,"culture-matsuri":610,"bj-meishi-koukan":614,"tech-mercari-merpay-id":618,"tech-mercari-microservices":622,"tech-mf-multitenant":626,"bj-nemawashi-ringi":630,"living-nenmatsu-chousei":634,"bj-1on1":638,"bj-online-kaigi":642,"culture-onsen":646,"culture-pro-baseball":650,"culture-ramen":654,"tech-recruit-data-platform":658,"law-roukikihou-kihon":662,"culture-sado":666,"culture-sandou":670,"culture-seasonal-events":674,"exam-sg":678,"bj-shagai-mail":682,"bj-shanai-mail":686,"culture-sumo":690,"culture-sushi":694,"culture-washoku":698,"law-yuukyuu-kyuuka":702,"kjh-k1-h04-anzen-kanri":706,"bill-one-auth":710,"contract-one-vision":714,"kjh-k1-h04-daisan-sha-teikyou":718,"eight-web-renewal":722,"kjh-k1-h04-gaikoku-kiroku":726,"kjh-k2-h04-gijutsu-jisshi":730,"kjh-k2-h04-gijutsu-kiso":733,"kjh-k1-h01-hotaikei":736,"kjh-k1-h06-hoyu-data":740,"kjh-k1-h07-kamei-kakou":744,"kjh-k1-h05-kanren-joho":748,"kjh-k1-h02-kihon-rinen":752,"kjh-k1-h09-jikkousei":756,"kjh-k1-h10-gyousei":760,"kjh-k1-h11-my-number-hogo":764,"kjh-k1-h11-my-number-sousoku":768,"kjh-k2-h01-guideline":772,"kjh-k2-h01-security-kiso":776,"kjh-k2-h02-anzen-kanri-sochi":780,"kjh-k2-h02-soshiki-kiso":784,"kjh-k2-h03-office":788,"kjh-k1-h03-riyou-mokuteki":792,"sansan-data-intelligence":796,"sansan-engineer-team-infra":800,"sansan-honne-15":804,"sansan-interview-110":808,"sansan-interview-126":812,"sansan-interview-127":816,"sansan-interview-130":820,"sansan-interview-40":824,"sansan-oyaco":828,"kjh-k1-h03-tekisei-shutoku":832,"kjh-k1-h08-tokumei-kakou":836},{"articleId":343,"path":344,"title":345},"culture-anime-studio-ghibli","\u002Farticles\u002Fculture\u002Fanime-studio-ghibli","スタジオジブリ作品史 — 宮崎駿・高畑勲・鈴木敏夫が築いた40年",{"articleId":347,"path":348,"title":349},"culture-bonsai-art","\u002Farticles\u002Fculture\u002Fbonsai-art","盆栽の世界 — 小宇宙を育てる日本の芸術",{"articleId":351,"path":352,"title":353},"tech-cybozu-kintone-no-code","\u002Farticles\u002Ftech\u002Fcybozu-kintone-no-code","kintoneのローコード戦略 — 業務アプリを誰でも作れる仕組み",{"articleId":355,"path":356,"title":357},"living-denki-gas-suidou","\u002Farticles\u002Fliving-in-japan\u002Fdenki-gas-suidou","電気・ガス・水道の契約 — 引越し時のライフライン手続き",{"articleId":359,"path":360,"title":361},"tech-gree-mobile-game-ops","\u002Farticles\u002Ftech\u002Fgree-mobile-game-ops","GREEのモバイルゲーム運用 — リアルタイム対戦と決済の裏側",{"articleId":363,"path":364,"title":365},"culture-green-tea-types","\u002Farticles\u002Fculture\u002Fgreen-tea-types","日本茶の種類と淹れ方 — 煎茶・玉露・抹茶の違い",{"articleId":367,"path":368,"title":369},"living-gym-fitness","\u002Farticles\u002Fliving-in-japan\u002Fgym-fitness","ジムとフィットネスクラブ — 入会から解約までの実務ガイド",{"articleId":371,"path":372,"title":373},"living-internet-hikari","\u002Farticles\u002Fliving-in-japan\u002Finternet-hikari-keiyaku","光回線とネット契約 — フレッツ・NURO・auひかり比較",{"articleId":375,"path":376,"title":377},"living-jisha-de-kau","\u002Farticles\u002Fliving-in-japan\u002Fjisha-de-kau","日本で不動産を買う — 外国人でも住宅ローンを組む方法",{"articleId":379,"path":380,"title":381},"exam-jlpt-n3-grammar","\u002Farticles\u002Fexams\u002Fjlpt-n3-grammar","JLPT N3 文法 — 初級から中級への橋渡し",{"articleId":383,"path":384,"title":385},"exam-jlpt-n3-vocab","\u002Farticles\u002Fexams\u002Fjlpt-n3-vocab","JLPT N3 語彙対策 — 1500語をどう攻略するか",{"articleId":387,"path":388,"title":389},"bj-job-gata-koyou","\u002Farticles\u002Fbusiness-japanese\u002Fjob-gata-koyou","ジョブ型雇用への移行 — メンバーシップ型からの脱却",{"articleId":391,"path":392,"title":393},"culture-kabuki-noh-bunraku","\u002Farticles\u002Fculture\u002Fkabuki-noh-bunraku","歌舞伎・能・文楽 — 日本三大伝統演劇の世界",{"articleId":395,"path":396,"title":397},"bj-karoushi-hatarakikata","\u002Farticles\u002Fbusiness-japanese\u002Fkaroushi-hatarakikata","過労死と働き方改革 — 残業規制の歴史と現状",{"articleId":399,"path":400,"title":401},"living-keitai-mobile-plan","\u002Farticles\u002Fliving-in-japan\u002Fkeitai-mobile-plan","携帯電話契約の選び方 — 大手キャリア・MVNO・eSIM完全ガイド",{"articleId":403,"path":404,"title":405},"living-konbini-atm-banking","\u002Farticles\u002Fliving-in-japan\u002Fkonbini-atm-banking","コンビニATMと電子マネー — 現金とキャッシュレスのハイブリッド生活",{"articleId":407,"path":408,"title":409},"living-kosodate-hoiku","\u002Farticles\u002Fliving-in-japan\u002Fkosodate-hoiku","子育て支援と保育園 — 児童手当・保活・無償化制度",{"articleId":411,"path":412,"title":413},"culture-nihon-teien","\u002Farticles\u002Fculture\u002Fnihon-teien","日本庭園の世界 — 池泉・枯山水・露地の様式",{"articleId":415,"path":416,"title":417},"bj-nomikai-survival","\u002Farticles\u002Fbusiness-japanese\u002Fnomikai-survival","飲み会・ノミニケーション完全攻略 — 新人エンジニアのサバイバルガイド",{"articleId":419,"path":420,"title":421},"tech-pixiv-image-cdn","\u002Farticles\u002Ftech\u002Fpixiv-image-cdn","pixivの画像配信基盤 — 数億イラストを世界に届ける技術",{"articleId":423,"path":424,"title":425},"culture-sake-shochu","\u002Farticles\u002Fculture\u002Fsake-shochu","日本酒と焼酎入門 — 製法・産地・飲み方の基礎",{"articleId":427,"path":428,"title":429},"bj-sankyu-ikukyu","\u002Farticles\u002Fbusiness-japanese\u002Fsankyu-ikukyu","産休・育休制度の実務 — 取得スケジュールと給付金",{"articleId":431,"path":432,"title":433},"tech-sansan-eight-platform","\u002Farticles\u002Ftech\u002Fsansan-eight-platform","Eight 名刺SaaSの基盤進化 — モバイルから法人向けプラットフォームへ",{"articleId":435,"path":436,"title":437},"culture-shichi-go-san","\u002Farticles\u002Fculture\u002Fshichi-go-san","七五三 — 子供の成長を祝う伝統行事",{"articleId":439,"path":440,"title":441},"bj-shukatsu-shinsotsu","\u002Farticles\u002Fbusiness-japanese\u002Fshukatsu-shinsotsu","新卒就活の流れ — エントリーシートから内定まで",{"articleId":443,"path":444,"title":445},"tech-smartnews-recommendation","\u002Farticles\u002Ftech\u002Fsmartnews-recommendation","SmartNewsの推薦システム — ニュースを最適化する機械学習",{"articleId":447,"path":448,"title":449},"bj-taishoku-todoke","\u002Farticles\u002Fbusiness-japanese\u002Ftaishoku-todoke","退職届と退職願 — 違いと書き方、円満退職への手順",{"articleId":451,"path":452,"title":453},"bj-telework-policy","\u002Farticles\u002Fbusiness-japanese\u002Ftelework-policy","テレワーク制度の現状 — コロナ後の在宅勤務とハイブリッド",{"articleId":455,"path":456,"title":457},"bj-tenshoku-resume","\u002Farticles\u002Fbusiness-japanese\u002Ftenshoku-resume","転職活動の進め方 — 履歴書と職務経歴書の書き方",{"articleId":459,"path":460,"title":461},"tech-yahoo-japan-search","\u002Farticles\u002Ftech\u002Fyahoo-japan-search","Yahoo! JAPAN検索の基盤 — 日本語特化の大規模検索システム",{"articleId":463,"path":464,"title":465},"culture-anime-business","\u002Farticles\u002Fculture\u002Fanime-business","アニメ・漫画文化と産業構造 — グローバル展開の現状",{"articleId":467,"path":468,"title":469},"exam-ap","\u002Farticles\u002Fexams\u002Fap","応用情報技術者試験 — 重点出題分野",{"articleId":471,"path":472,"title":473},"exam-aws-japan","\u002Farticles\u002Fexams\u002Faws-japan","AWS認定 — 日本語受験のコツ",{"articleId":475,"path":476,"title":477},"law-chosakuken","\u002Farticles\u002Flaw\u002Fchosakuken","著作権法 — エンジニアが知っておくべき基礎",{"articleId":479,"path":480,"title":481},"tech-cookpad-recipe-search","\u002Farticles\u002Ftech\u002Fcookpad-recipe-search-ranking","Cookpadのレシピ検索 — 学習to-rank実装",{"articleId":483,"path":484,"title":485},"tech-cybozu-kintone-api","\u002Farticles\u002Ftech\u002Fcybozu-kintone-api-design","kintone API設計の十年 — 後方互換性との戦い",{"articleId":487,"path":488,"title":489},"tech-dena-observability","\u002Farticles\u002Ftech\u002Fdena-mobile-game-observability","DeNAのモバイルゲーム監視基盤",{"articleId":491,"path":492,"title":493},"law-denshi-chouho","\u002Farticles\u002Flaw\u002Fdenshi-chouho","電子帳簿保存法 — スキャナ保存と電子取引保存の対応",{"articleId":495,"path":496,"title":497},"tech-digital-cho-cloud","\u002Farticles\u002Ftech\u002Fdigital-cho-government-cloud","デジタル庁ガバメントクラウド技術詳細",{"articleId":499,"path":500,"title":501},"exam-fe","\u002Farticles\u002Fexams\u002Ffe","基本情報技術者試験 — シラバス全体像",{"articleId":503,"path":504,"title":505},"tech-freee-accounting","\u002Farticles\u002Ftech\u002Ffreee-accounting-integrity","freeeの会計データ整合性 — 仕訳バランスの自動検証",{"articleId":507,"path":508,"title":509},"law-furiransu-hou","\u002Farticles\u002Flaw\u002Ffuriransu-hou","フリーランス保護法（2024年施行）— 取引適正化のポイント",{"articleId":511,"path":512,"title":513},"law-harassment","\u002Farticles\u002Flaw\u002Fharassment","ハラスメント関連法 — パワハラ・セクハラ・マタハラ防止義務",{"articleId":515,"path":516,"title":517},"tech-hatena-mackerel","\u002Farticles\u002Ftech\u002Fhatena-mackerel-alert-design","MackerelのAlert設計思想",{"articleId":519,"path":520,"title":521},"bj-hourensou","\u002Farticles\u002Fbusiness-japanese\u002Fhourensou","報・連・相 — 日本企業のコミュニケーションの基本",{"articleId":523,"path":524,"title":525},"bj-hyouka-mendan","\u002Farticles\u002Fbusiness-japanese\u002Fhyouka-mendan","評価面談の準備と振り返り",{"articleId":527,"path":528,"title":529},"law-invoice","\u002Farticles\u002Flaw\u002Finvoice-seido","インボイス制度の仕組みと実務 — 適格請求書発行事業者",{"articleId":531,"path":532,"title":533},"exam-it-passport","\u002Farticles\u002Fexams\u002Fit-passport","ITパスポート試験 — 概要と学習法",{"articleId":535,"path":536,"title":537},"culture-izakaya","\u002Farticles\u002Fculture\u002Fizakaya","居酒屋文化と乾杯のマナー — お通しから締めまで",{"articleId":539,"path":540,"title":541},"culture-j-league","\u002Farticles\u002Fculture\u002Fj-league","Jリーグの歴史と地域密着 — 1993年開幕から30年",{"articleId":543,"path":544,"title":545},"culture-jinja-tera","\u002Farticles\u002Fculture\u002Fjinja-tera","神社と寺の違い、参拝マナー",{"articleId":547,"path":548,"title":549},"exam-jlpt-n1-dokkai","\u002Farticles\u002Fexams\u002Fjlpt-n1-dokkai","JLPT N1 — 読解問題のアプローチ",{"articleId":551,"path":552,"title":553},"exam-jlpt-n2-business","\u002Farticles\u002Fexams\u002Fjlpt-n2-business","JLPT N2 — ビジネス語彙集中対策",{"articleId":555,"path":556,"title":557},"bj-kaigi-manner","\u002Farticles\u002Fbusiness-japanese\u002Fkaigi-manner","会議のマナーと進め方 — 司会から議事録まで",{"articleId":559,"path":560,"title":561},"living-kakutei-shinkoku","\u002Farticles\u002Fliving-in-japan\u002Fkakutei-shinkoku","確定申告の基本 — 給与所得・副業・控除",{"articleId":563,"path":564,"title":565},"bj-keigo-kihon","\u002Farticles\u002Fbusiness-japanese\u002Fkeigo-kihon","ビジネス敬語の基本 — 尊敬語・謙譲語・丁寧語の使い分け",{"articleId":567,"path":568,"title":569},"law-keihin-hyouji","\u002Farticles\u002Flaw\u002Fkeihin-hyouji","改正景品表示法とステマ規制 — マーケティングの法的注意点",{"articleId":571,"path":572,"title":573},"living-kenkou-hoken","\u002Farticles\u002Fliving-in-japan\u002Fkenkou-hoken","健康保険の入門 — 国保と社保の違い",{"articleId":575,"path":576,"title":577},"living-kosei-nenkin","\u002Farticles\u002Fliving-in-japan\u002Fkosei-nenkin","厚生年金と国民年金 — 老後の備えと現役の負担",{"articleId":579,"path":580,"title":581},"tech-line-llmops","\u002Farticles\u002Ftech\u002Fline-llmops","LINEのLLMOps — 大規模言語モデル運用の取り組み",{"articleId":583,"path":584,"title":585},"tech-line-streaming","\u002Farticles\u002Ftech\u002Fline-streaming","LINEの大規模リアルタイム配信基盤",{"articleId":587,"path":588,"title":589},"living-chintai-keiyaku","\u002Farticles\u002Fliving-in-japan\u002Fliving-chintai-keiyaku","賃貸契約と保証会社 — 礼金・敷金から保証料まで",{"articleId":591,"path":592,"title":593},"living-eijuken","\u002Farticles\u002Fliving-in-japan\u002Fliving-eijuken","永住権申請の最新基準 — 一般・高度専門職ルート比較",{"articleId":595,"path":596,"title":597},"living-engineer-visa","\u002Farticles\u002Fliving-in-japan\u002Fliving-engineer-visa","エンジニアの在留資格 — 「技術・人文知識・国際業務」ビザの取得手順",{"articleId":599,"path":600,"title":601},"living-ginkou-koza","\u002Farticles\u002Fliving-in-japan\u002Fliving-ginkou-koza","銀行口座開設とクレジットカード — 外国人エンジニアの実務",{"articleId":603,"path":604,"title":605},"living-hikkoshi-checklist","\u002Farticles\u002Fliving-in-japan\u002Fliving-hikkoshi-checklist","引越し手続きチェックリスト — 役所・ライフライン・住所変更",{"articleId":607,"path":608,"title":609},"living-koudo-senmon","\u002Farticles\u002Fliving-in-japan\u002Fliving-koudo-senmon","高度専門職ビザの実務 — ポイント制度と特権",{"articleId":611,"path":612,"title":613},"culture-matsuri","\u002Farticles\u002Fculture\u002Fmatsuri","日本の祭り — 季節と地域の象徴",{"articleId":615,"path":616,"title":617},"bj-meishi-koukan","\u002Farticles\u002Fbusiness-japanese\u002Fmeishi-koukan","名刺交換の作法 — 第一印象を決める数十秒",{"articleId":619,"path":620,"title":621},"tech-mercari-merpay-id","\u002Farticles\u002Ftech\u002Fmercari-merpay-id","メルペイのID基盤 — eKYC・本人確認の技術",{"articleId":623,"path":624,"title":625},"tech-mercari-microservices","\u002Farticles\u002Ftech\u002Fmercari-microservices-migration","Mercariのマイクロサービス移行 — モノリスから次世代へ",{"articleId":627,"path":628,"title":629},"tech-mf-multitenant","\u002Farticles\u002Ftech\u002Fmoneyforward-multitenant-saas","Money Forwardのマルチテナント設計 — データ分離とセキュリティ",{"articleId":631,"path":632,"title":633},"bj-nemawashi-ringi","\u002Farticles\u002Fbusiness-japanese\u002Fnemawashi-ringi","根回しと稟議 — 日本企業の意思決定の仕組み",{"articleId":635,"path":636,"title":637},"living-nenmatsu-chousei","\u002Farticles\u002Fliving-in-japan\u002Fnenmatsu-chousei","年末調整の仕組み — 会社員のための税精算",{"articleId":639,"path":640,"title":641},"bj-1on1","\u002Farticles\u002Fbusiness-japanese\u002Fone-on-one","1on1ミーティングの活用法 — 上司と部下の対話",{"articleId":643,"path":644,"title":645},"bj-online-kaigi","\u002Farticles\u002Fbusiness-japanese\u002Fonline-kaigi","オンライン会議のエチケット — Zoom時代のビジネスマナー",{"articleId":647,"path":648,"title":649},"culture-onsen","\u002Farticles\u002Fculture\u002Fonsen","温泉文化と入浴マナー — 名湯巡りの楽しみ方",{"articleId":651,"path":652,"title":653},"culture-pro-baseball","\u002Farticles\u002Fculture\u002Fpro-baseball","プロ野球と高校野球 — 国民的スポーツの二つの顔",{"articleId":655,"path":656,"title":657},"culture-ramen","\u002Farticles\u002Fculture\u002Framen","ラーメン地域ごとの違い — 札幌・博多・喜多方",{"articleId":659,"path":660,"title":661},"tech-recruit-data-platform","\u002Farticles\u002Ftech\u002Frecruit-data-platform","Recruit データ基盤刷新事例 — 数十サービスの統合",{"articleId":663,"path":664,"title":665},"law-roukikihou-kihon","\u002Farticles\u002Flaw\u002Froukikihou-kihon","労働基準法の基本 — 労働時間・休憩・残業規制",{"articleId":667,"path":668,"title":669},"culture-sado","\u002Farticles\u002Fculture\u002Fsado","茶道入門 — 千利休と侘び寂びの精神",{"articleId":671,"path":672,"title":673},"culture-sandou","\u002Farticles\u002Fculture\u002Fsandou","茶華書三道 — 日本の精神を体現する三つの道",{"articleId":675,"path":676,"title":677},"culture-seasonal-events","\u002Farticles\u002Fculture\u002Fseasonal-events","季節の行事 — 正月から年末まで日本の年中行事",{"articleId":679,"path":680,"title":681},"exam-sg","\u002Farticles\u002Fexams\u002Fsg","情報セキュリティマネジメント試験 — 管理者向けセキュリティ",{"articleId":683,"path":684,"title":685},"bj-shagai-mail","\u002Farticles\u002Fbusiness-japanese\u002Fshagai-mail","社外メールの書き方 — お詫び・依頼・確認",{"articleId":687,"path":688,"title":689},"bj-shanai-mail","\u002Farticles\u002Fbusiness-japanese\u002Fshanai-mail","社内メールの書き方 — 件名から結びまで",{"articleId":691,"path":692,"title":693},"culture-sumo","\u002Farticles\u002Fculture\u002Fsumo","大相撲 — 番付と力士の生活",{"articleId":695,"path":696,"title":697},"culture-sushi","\u002Farticles\u002Fculture\u002Fsushi","寿司の歴史と種類 — なれずしから江戸前まで",{"articleId":699,"path":700,"title":701},"culture-washoku","\u002Farticles\u002Fculture\u002Fwashoku","和食 — ユネスコ無形文化遺産と一汁三菜",{"articleId":703,"path":704,"title":705},"law-yuukyuu-kyuuka","\u002Farticles\u002Flaw\u002Fyuukyuu-kyuuka","有給休暇の取得ルールと最新改正",{"articleId":707,"path":708,"title":709},"kjh-k1-h04-anzen-kanri","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fanzen-kanri","課題Ⅰ 第４編① 個人データに関する義務 ― 正確性の確保・安全管理措置・漏えい報告",{"articleId":711,"path":712,"title":713},"bill-one-auth","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fbill-one-auth","インボイス管理サービスBill Oneの認証を内製認証基盤に置き換えて認証基盤のコストを削減した話",{"articleId":715,"path":716,"title":717},"contract-one-vision","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fcontract-one-vision","契約書を\"意思決定のインフラ\"に──Contract Oneで挑む、新たな価値創造",{"articleId":719,"path":720,"title":721},"kjh-k1-h04-daisan-sha-teikyou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fdaisan-sha-teikyou","課題Ⅰ 第４編② 第三者提供の制限 ― 同意・オプトアウト・非該当類型",{"articleId":723,"path":724,"title":725},"eight-web-renewal","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Feight-web-renewal","Web版Eightのリニューアルと、安全なリリースのための取り組み",{"articleId":727,"path":728,"title":729},"kjh-k1-h04-gaikoku-kiroku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fgaikoku-kiroku","課題Ⅰ 第４編③ 外国にある第三者への提供の制限・記録義務・確認義務（法28条〜30条）",{"articleId":112,"path":731,"title":732},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fgijutsu-jisshi","課題Ⅱ 第４編② 技術的安全管理措置の実施項目",{"articleId":11,"path":734,"title":735},"\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fgijutsu-kiso","課題Ⅱ 第４編① 技術的セキュリティ対策の基礎知識",{"articleId":737,"path":738,"title":739},"kjh-k1-h01-hotaikei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fhotaikei","課題Ⅰ 第１編 個人情報保護の法体系と各種認定制度",{"articleId":741,"path":742,"title":743},"kjh-k1-h06-hoyu-data","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fhoyu-data","課題Ⅰ 第６編 保有個人データに関する義務",{"articleId":745,"path":746,"title":747},"kjh-k1-h07-kamei-kakou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkamei-kakou","課題Ⅰ 第７編 仮名加工情報（法41条・42条）",{"articleId":749,"path":750,"title":751},"kjh-k1-h05-kanren-joho","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkanren-joho","課題Ⅰ 第５編 個人関連情報に関する義務（法31条）",{"articleId":753,"path":754,"title":755},"kjh-k1-h02-kihon-rinen","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkihon-rinen","課題Ⅰ 第２編 個人情報保護法の目的・基本理念と用語の定義",{"articleId":757,"path":758,"title":759},"kjh-k1-h09-jikkousei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h09-jikkousei","課題Ⅰ 第９編 実効性を担保する仕組み等",{"articleId":761,"path":762,"title":763},"kjh-k1-h10-gyousei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h10-gyousei","課題Ⅰ 第10編 行政機関等における個人情報等の取扱い",{"articleId":765,"path":766,"title":767},"kjh-k1-h11-my-number-hogo","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h11-my-number-hogo","課題Ⅰ 第11編② マイナンバー法 ― 特定個人情報の提供制限・保護・監督・罰則（法19条〜57条）",{"articleId":769,"path":770,"title":771},"kjh-k1-h11-my-number-sousoku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h11-my-number-sousoku","課題Ⅰ 第11編① マイナンバー法 ― 総則・個人番号・個人番号カード（法1条〜18条の5）",{"articleId":773,"path":774,"title":775},"kjh-k2-h01-guideline","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h01-guideline","課題Ⅱ 第１編② セキュリティ対策基準とガイドライン",{"articleId":777,"path":778,"title":779},"kjh-k2-h01-security-kiso","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h01-security-kiso","課題Ⅱ 第１編① 情報セキュリティの基礎と脅威",{"articleId":781,"path":782,"title":783},"kjh-k2-h02-anzen-kanri-sochi","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h02-anzen-kanri-sochi","課題Ⅱ 第２編② 組織的・人的セキュリティ ― 安全管理措置・委託先監督・事故対応",{"articleId":785,"path":786,"title":787},"kjh-k2-h02-soshiki-kiso","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h02-soshiki-kiso","課題Ⅱ 第２編① 組織的・人的セキュリティ ― 基本方針の策定からリスク管理・規程整備まで",{"articleId":789,"path":790,"title":791},"kjh-k2-h03-office","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Foffice","課題Ⅱ 第３編 オフィスセキュリティ",{"articleId":793,"path":794,"title":795},"kjh-k1-h03-riyou-mokuteki","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Friyou-mokuteki","課題Ⅰ 第３編① 利用目的の特定・変更と利用目的による制限、不適正な利用の禁止",{"articleId":797,"path":798,"title":799},"sansan-data-intelligence","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-data-intelligence","Sansan Data Intelligenceリリースに寄せて",{"articleId":801,"path":802,"title":803},"sansan-engineer-team-infra","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-engineer-team-infra","Sansan Engineer Team：インフラ戦略部",{"articleId":805,"path":806,"title":807},"sansan-honne-15","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-honne-15","入社後のホンネ［技術本部 データ戦略部 Infrastructureグループ 渡邉 友］",{"articleId":809,"path":810,"title":811},"sansan-interview-110","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-110","SIer出身者が活躍する理由とは。Sansanを牽引するプロダクト開発に挑み続ける",{"articleId":813,"path":814,"title":815},"sansan-interview-126","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-126","AIと協働する開発組織、そして技術の深化。Sansan 新CTO笹川が語るビジョン",{"articleId":817,"path":818,"title":819},"sansan-interview-127","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-127","Sansanの技術基盤を関西から築く。新設組織で未来を創る、エンジニアの挑戦",{"articleId":821,"path":822,"title":823},"sansan-interview-130","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-130","Sansanの全社基盤を支えるPlatform Engineering Unitの挑戦",{"articleId":825,"path":826,"title":827},"sansan-interview-40","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-40","膨大な量のデータを平然と処理する。Sansanのインフラのすごさが、そこに表れている。",{"articleId":829,"path":830,"title":831},"sansan-oyaco","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-oyaco","仕事と子育ての両立を支援する制度「OYACO」",{"articleId":833,"path":834,"title":835},"kjh-k1-h03-tekisei-shutoku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Ftekisei-shutoku","課題Ⅰ 第３編② 適正な取得・要配慮個人情報・利用目的の通知",{"articleId":837,"path":838,"title":839},"kjh-k1-h08-tokumei-kakou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Ftokumei-kakou","課題Ⅰ 第８編 匿名加工情報に関する義務等（法43条〜46条）"]