{"data":{"id":"SC-18","name":"Mobile Code","family":"SC","family_name":"System and Communications Protection","withdrawn":false,"description":"a. Define acceptable and unacceptable mobile code and mobile code technologies; and\nb. Authorize, monitor, and control the use of mobile code within the system.","supplemental_guidance":"Mobile code includes any program, application, or content that can be transmitted across a network (e.g., embedded in an email, document, or website) and executed on a remote system. Decisions regarding the use of mobile code within organizational systems are based on the potential for the code to cause damage to the systems if used maliciously. Mobile code technologies include Java applets, JavaScript, HTML5, WebGL, and VBScript. Usage restrictions and implementation guidelines apply to both the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations and devices, including notebook computers and smart phones. Mobile code policy and procedures address specific actions taken to prevent the development, acquisition, and introduction of unacceptable mobile code within organizational systems, including requiring mobile code to be digitally signed by a trusted source.","enhancements":[{"id":"SC-18(01)","name":"Identify Unacceptable Code and Take Corrective Actions","statement":"Identify [Assignment: organization-defined unacceptable mobile code] and take [Assignment: organization-defined corrective actions].","baselines":[]},{"id":"SC-18(02)","name":"Acquisition, Development, and Use","statement":"Verify that the acquisition, development, and use of mobile code to be deployed in the system meets [Assignment: organization-defined mobile code requirements].","baselines":[]},{"id":"SC-18(03)","name":"Prevent Downloading and Execution","statement":"Prevent the download and execution of [Assignment: organization-defined unacceptable mobile code].","baselines":[]},{"id":"SC-18(04)","name":"Prevent Automatic Execution","statement":"Prevent the automatic execution of mobile code in [Assignment: organization-defined software applications] and enforce [Assignment: organization-defined actions] prior to executing the code.","baselines":[]},{"id":"SC-18(05)","name":"Allow Execution Only in Confined Environments","statement":"Allow execution of permitted mobile code only in confined virtual machine environments.","baselines":[]}],"baseline_low":false,"baseline_moderate":true,"baseline_high":true,"nist_800_53":{"rev5":{"id":"SC-18","name":"Mobile Code","description":"a. Define acceptable and unacceptable mobile code and mobile code technologies; and\nb. Authorize, monitor, and control the use of mobile code within the system.","discussion":"Mobile code includes any program, application, or content that can be transmitted across a network (e.g., embedded in an email, document, or website) and executed on a remote system. Decisions regarding the use of mobile code within organizational systems are based on the potential for the code to cause damage to the systems if used maliciously. Mobile code technologies include Java applets, JavaScript, HTML5, WebGL, and VBScript. Usage restrictions and implementation guidelines apply to both the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations and devices, including notebook computers and smart phones. Mobile code policy and procedures address specific actions taken to prevent the development, acquisition, and introduction of unacceptable mobile code within organizational systems, including requiring mobile code to be digitally signed by a trusted source.","related_controls":["AU-02","AU-12","CM-02","CM-06","SI-03"],"baseline_low":false,"baseline_moderate":true,"baseline_high":true,"baseline_privacy":false,"new_in_rev5":false,"changes_from_rev4":"Control text replaces requirement to establish usage restrictions and implementation guidance with requirement to authorize, monitor, and control the use of mobile code within the system Discussion expanded with additional examples of mobile code and factors that should be included in mobile code policy and procedures"}},"compliance_mappings":{"iso_27001_2022":[],"iso_27002_2022":[],"cobit_2019":[],"pci_dss_v4":["6.4.3","11.6.1"],"nist_csf_2":[],"cis_controls_v8":[],"soc2_tsc":[],"finos_ccc":[],"iso_42001_2023":[],"iec_62443":["3-3 SR 2.4"],"asd_e8":["E8-3","E8-3 ML2","E8-4","E8-4 ML1"],"nis2":[],"apra_cps_234":[],"mas_trm":[],"pra_op_resilience":[],"bsi_grundschutz":["APP.1.1"],"anssi":["Hygiene.20","Hygiene.22","SecNumCloud.13.1"],"osfi_b13":["B-13.3.2"],"finma_circular":["IV.B.d(59)","IV.C(64)"],"gdpr":["Art.32(1)(b)"],"dora":["Art.9(4)(e)"],"bio2":[],"rbi_csf":[],"fisc":["FISC.T8"],"lgpd_bcb":[],"hkma_tme1":[],"mlps_2":[],"dnb_good_practice":["DNB.19.1"],"cra":[],"swift_cscf":[],"nca_ecc":["2-3"],"ffiec_is":["II.C.12"],"sebi_cscrf":["PR.ES"],"cmmc_2":["SC"],"nerc_cip":[],"nrc_73_54":[],"tsa_psd":[],"ieee_1686":[],"ferc_cip":[],"doe_c2m2":[],"api_1164":[],"awia":[],"iaea_nss":[],"pci_pts":[],"fips_140":[],"cbest":[],"tiber_eu":[],"pci_hsm":[],"common_criteria":[],"isae_3402":[],"fca_sysc_13":[],"fda_21_cfr_11":[],"fda_cyber":[],"hitrust_csf":[],"iso_27799":[],"lloyds_ms":["MS8.10"],"naic_ds":[],"nhs_dspt":["NDG-9.3","NDG-9.5"],"pra_ss1_23":[],"solvency_ii":[],"owasp_masvs_v2":["MASVS-CODE-4"],"csa_ccm_v4":[],"csa_aicm":[],"ccss_v9":[],"mica":[],"basel_sco60":[],"bssc":[],"sec_custody_digital":[],"dpdpa":[],"nist_ai_rmf_1":[],"eu_ai_act":[],"nist_800_171_r3":["03.13.13"],"nist_ssdf":[],"owasp_agentic_top10_2026":["ASI05"],"ncsc_caf":[],"owasp_llm_top10_2026":["LLM10"],"bsi_grundschutz_pp":["SENS.7.9","KONF.3.8","KONF.6.14","KONF.6.15","KONF.7.12","KONF.12.1","KONF.13.1"],"bot_cyber":[],"bsi_c5":[]},"metadata":{"last_reviewed":"2026-10-03","review_notes":"2026-10-03: baselines LMH to -MH, from NIST SP 800-53B Release 5.2.0.","mapping_status":"complete"},"function":"preventative","used_by_patterns":["SP-001","SP-002","SP-011"],"attack":{"techniques":38,"route":"/api/v1/controls/SC-18?fields=attack"}}}