Israeli cybersecurity regulatory framework guidance covering INCD (Ma'arach HaSyber) national directives, Bank of Israel Directive 361 (cyber for financial institutions), Directive 357 (payment security), ISA requirements for TASE-listed companies, and sector-specific rules for fintech and healthtech. Use when user asks about cyber regulation Israel, INCD compliance, Bank of Israel directives, ISA cyber requirements, or sector cyber rules. Do NOT use for privacy law compliance (use israeli-privacy-compliance instead).
Trust score 89/100 (Trusted) · 37+ installs · 2 GitHub contributors · MIT license
Israeli cybersecurity regulation evolves rapidly, with specific requirements from the National Cyber Directorate, the Privacy Protection Authority, and sector-specific regulators. Businesses struggle to track all relevant guidelines, regulations, and standards, and to understand how they actually apply to their organization in practice.
npx skills-il add skills-il/security-compliance@v1.0.3-israeli-cyber-regulations --skill israeli-cyber-regulations -a claude-codeWe are a small bank and need to comply with Bank of Israel Directive 361. What are the main requirements we need to implement and where do we start?
What are the latest National Cyber Directorate guidelines for organizations in critical infrastructure and how do I implement them practically?
Help me perform a gap analysis between our current information security posture and Israeli cyber regulatory requirements
Added Reference Links section pointing to official sources for fact verification.
Apr 15, 2026
Audit and ensure Israeli e-commerce legal compliance — Consumer Protection Law, return policies, price display, accessibility, and cookie consent. Use when user asks about "online store compliance Israel", "Chok Hagnat HaTzarchan", "consumer protection Israel", "return policy Israel", "IS 5568 ecommerce", "cookie consent Israel", or "חוק הגנת הצרכן". Covers cooling-off period validation, price display requirements, Hebrew terms of service generation, accessibility compliance (IS 5568), and business disclosure verification. Do NOT use for food-specific compliance (use israeli-food-business-compliance) or privacy/GDPR (use israeli-privacy-shield).
Guide Israeli ML teams through the AI governance and compliance stack: Ministry of Innovation December 2023 AI policy principles, Privacy Protection Law (PPL) and Amendment 13 applied to ML training data, sector-specific rules (Bank of Israel Directive 364, Ministry of Health AMAR medical-device AI), and EU AI Act exposure for Israeli exporters. Generates model cards, data statements, and DPIA templates tailored to Israeli context. Use when preparing AI governance docs, answering an enterprise customer's AI risk review, classifying a system under the EU AI Act, or building an internal responsible-AI checklist. Prevents costly compliance gaps when shipping AI to regulated markets. Do NOT use for general PPL policy (use israeli-privacy-shield), web app security (use israeli-appsec-scanner), or SOC/threat triage (use israeli-cybersecurity-ops).
Check whether a product requires Standards Institution of Israel (SII / Mechon HaTikanim) approval under an official standard (takan rishmi) before it can be imported into Israel. Returns applicable SI numbers, approval route (type approval, shipment approval, Maslol Plus declaration, EU-CoC recognition), required lab tests, timelines, and fast-track options based on the 2016 food parallel-import reform and the 2022/2025 electronics + EU-regulation reforms. Use when a user asks about importing electronics, toys, cosmetics, food-contact materials, vehicles, or building materials into Israel, asks about CE/type approval, or has a shipment stuck at Israeli customs. Do NOT use for customs duty calculation (use israeli-customs-duty-calculator) or for general product safety review outside the Israeli regulatory context.
Want to build your own skill? Try the Skill Creator · Submit a Skill