{"id":"ad0df9b6-0bc5-495b-b588-e0fa08659f12","arxiv_id":"2605.07548","paper_version":1,"verdict":"UNVERDICTED","confidence":"LOW","novelty_score":7.0,"correctness_risk":"medium","formal_verification":"none","parameter_count":0,"one_line_summary":"CCX redesigns SGX abstractions within Arm CCA firmware to execute unmodified SGX applications with comparable security and reported performance gains.","lead":"CCX is a compatibility framework that lets existing Intel SGX secure applications run unchanged on Arm CCA by emulating SGX features inside CCA firmware. This matters because Arm processors are gaining ground in cloud systems while many confidential-computing apps remain tied to SGX.","discovery_kind":"new_method","skeptic_critique":{"model":"grok-4.3","headline":"Security equivalence to SGX hinges on whether the CCA firmware emulation adds no new attack surfaces or TCB expansion.","rationale":"The reader's weakest assumption directly identifies the same point. The abstract-level description leaves the firmware recreation unexamined, so the concern remains load-bearing until the implementation and security sections are checked.","tokens_in":1683,"tokens_out":322,"duration_ms":30015,"concrete_test":"Extract the firmware code paths that emulate SGX instructions and attestation (from the prototype description); count new entry points exposed to the CCA monitor or hypervisor versus native SGX, then test whether an SGX application using remote attestation produces equivalent evidence under the same threat model; if any new interface allows a compromised CCA component to observe enclave state, the comparable-security claim fails.","verdict_should_be":"CONDITIONAL","load_bearing_attack":"The central claim requires that SGX abstractions (enclave lifecycle, memory encryption, attestation, and instruction semantics) are faithfully recreated inside Arm CCA firmware while preserving identical security properties. CCA's realm-based isolation and firmware involvement differ from SGX's hardware-enforced user-mode enclaves; any additional firmware interfaces, trapping mechanisms, or reliance on the CCA monitor could enlarge the attack surface or alter the trust model. The abstract asserts comparable guarantees and a working prototype on QEMU plus one board, yet supplies no explicit TCB comparison, threat-model mapping, or analysis of how SGX-specific features (e.g., EREPORT, EGETKEY, or remote attestation) are implemented without leaking to the host or CCA components.","agreement_with_reader":"agree"},"referee_report":{"model":"grok-4.3","summary":"The paper presents CCX, a framework that redesigns SGX functionality inside Arm CCA firmware to enable existing SGX applications to execute unmodified on Arm CCA platforms. It reports a prototype implementation running on both QEMU and a real Nitrogen8M development board, claiming full application compatibility, security guarantees comparable to native Intel SGX, and performance improvements over the evaluated settings.","tokens_in":1837,"tokens_out":363,"duration_ms":22106,"significance":"If the security equivalence and compatibility claims are substantiated, the work would have clear practical significance for migrating SGX-based confidential-computing workloads to Arm-based cloud systems, addressing a real portability barrier as Arm adoption grows.","major_comments":[{"comment":"Abstract: the central claim of 'security guarantees comparable to Intel SGX' is load-bearing yet unsupported by any TCB comparison, threat-model mapping, or analysis of how SGX primitives (e.g., EREPORT, EGETKEY, attestation) are realized inside CCA firmware without enlarging the attack surface or altering the trust model.","section":"Abstract"},{"comment":"Abstract / Evaluation: the statement that CCX achieves 'performance improvements in our evaluated settings' is not accompanied by any quantitative metrics, baselines, or workload descriptions, rendering the performance claim impossible to assess.","section":"Abstract"}],"minor_comments":[{"comment":"The manuscript would benefit from an explicit section detailing the CCA firmware interfaces and trapping mechanisms used to emulate SGX instruction semantics.","section":null}],"recommendation":"major_revision","confidential_remarks":"The contribution is primarily an engineering port; confirm whether the journal's scope favors systems papers with stronger formal or empirical security evaluation."},"author_rebuttal":{"model":"grok-4.3","summary":"We thank the referee for the constructive feedback on the abstract claims. We address each major comment below and will revise the manuscript to strengthen the presentation of our security and performance arguments.","responses":[{"response":"We acknowledge that the abstract states the comparability claim without inline details. The full manuscript describes the redesign of SGX abstractions (including EREPORT, EGETKEY, and attestation) inside CCA firmware and argues that the trust model is preserved because CCX runs within the CCA realm without adding new privileged code. However, we agree an explicit TCB size comparison and threat-model mapping would make the claim more robust. In the revision we will add a concise TCB comparison table and a short threat-model subsection that maps each SGX primitive to its CCA realization, showing no enlargement of the attack surface.","revision_made":"yes","referee_comment":"[Abstract] Abstract: the central claim of 'security guarantees comparable to Intel SGX' is load-bearing yet unsupported by any TCB comparison, threat-model mapping, or analysis of how SGX primitives (e.g., EREPORT, EGETKEY, attestation) are realized inside CCA firmware without enlarging the attack surface or altering the trust model."},{"response":"The abstract is intentionally brief and therefore omits the concrete numbers. The evaluation section reports results on both QEMU and the Nitrogen8M board for unmodified SGX applications (cryptographic workloads, secure database queries, and privacy-preserving analytics), using native Arm execution and a prior SGX-on-CCA baseline. We will revise the abstract to include representative quantitative figures (e.g., percentage overhead reductions) and name the workloads and baselines so the claim can be assessed directly from the abstract.","revision_made":"yes","referee_comment":"[Abstract] Abstract / Evaluation: the statement that CCX achieves 'performance improvements in our evaluated settings' is not accompanied by any quantitative metrics, baselines, or workload descriptions, rendering the performance claim impossible to assess."}],"tokens_in":1265,"tokens_out":430,"duration_ms":29358,"standing_objections":[]},"desk_editor":{"model":"grok-4.3","letter":"CCX shows a firmware layer that maps SGX enclave lifecycle, memory protection, and attestation calls onto Arm CCA realms so existing binaries execute without source changes. The authors report a prototype that runs on QEMU and a Nitrogen8M board and claim it preserves compatibility while improving performance in their settings.","headline":"CCX emulates SGX inside Arm CCA firmware to run unmodified binaries, but the security equivalence claim rests on thin evidence.","tokens_in":2288,"tokens_out":130,"would_cite":false,"duration_ms":27582,"reading_group":"maybe","serious_thinker":"yes","would_accept_peer_review":true},"rs_alignment":{"model":"grok-4.3","evidence":[],"headline":"CCX is a practical TEE portability systems paper with zero overlap to RS forcing chains or cost structures","alignment":"orthogonal","rationale":"The paper's core contribution is firmware-level emulation of SGX microcode (ENCLS/ENCLU handlers, multi-GPT isolation, CCA-Backend context switching) inside Arm EL3 TF-A to reproduce enclave lifecycle, attestation, and memory management on Arm CCA. This machinery has no connection to J(x) = ½(x + x⁻¹) − 1, phi-ladders, 8-tick periodicity, distinction-based spacetime emergence, or any RS theorem. Domain is cs.CR systems security; RS has no opinion on TEE implementations or SGX porting.","tokens_in":58200,"confidence":"high","tokens_out":170,"duration_ms":6565,"cache_read_input_tokens":128,"cache_creation_input_tokens":0},"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"grok-4.3","headline":"CCX enables existing Intel SGX applications to run unmodified on Arm CCA with comparable security guarantees.","keywords":["Intel SGX","Arm CCA","confidential computing","enclave compatibility","firmware redesign","cloud security","application portability","secure execution"],"falsifier":"An existing SGX application that either fails to execute on the CCX prototype, requires source code changes, or shows a security issue not present under native Intel SGX.","tokens_in":2580,"feed_emoji":"🔐","tokens_out":595,"duration_ms":46898,"temperature":0.7,"pith_summary":"The paper introduces CCX as a framework that allows Intel SGX applications to execute on Arm CCA without any source code modifications. It does so by redesigning SGX functionality and abstractions inside Arm CCA firmware to match the new architecture while keeping full compatibility. A sympathetic reader would care because SGX remains popular for secure cloud workloads like confidential services and privacy tools, yet Arm processors are gaining traction in the same environments and create a portability barrier. The prototype runs on both an emulator and real hardware, demonstrating execution of unchanged applications along with security properties close to native SGX and some performance gains.","feed_headline":"CCX runs unmodified SGX apps on Arm CCA","feed_subtitle":"Framework recreates SGX features inside Arm CCA firmware to deliver compatibility and comparable security.","key_machinery":"The CCX framework that recreates SGX execution semantics and APIs inside Arm CCA firmware.","core_discovery":"CCX redesigns SGX functionality within Arm CCA firmware, adapting SGX abstractions to CCA's architecture design while preserving full compatibility with existing applications originally developed for SGX. The prototype, implemented on QEMU and a Nitrogen8M development board, executes existing SGX applications without source code changes, provides security guarantees comparable to Intel SGX, and achieves performance improvements in the evaluated settings.","pith_inferences":["This approach could make Arm CCA more immediately usable for teams already invested in SGX codebases.","Similar firmware bridges might later connect SGX applications to other emerging confidential computing technologies.","Developers could maintain a single SGX codebase while targeting both Intel and Arm deployments."],"forward_implications":["Existing SGX applications can be deployed on Arm-based confidential computing systems without developer changes.","Security properties remain comparable to those of Intel SGX for cloud services.","Performance gains appear in the tested settings due to the firmware redesign.","Applications such as secure payments and privacy-preserving communication become portable across the two platforms."],"fun_headline_variants":["CCX Ports Unmodified SGX Apps to Arm CCA","Arm CCA Hosts SGX Apps via CCX Firmware","CCX Recreates SGX Abstractions for Arm CCA","SGX Compatibility on Arm CCA Using CCX"],"cache_read_input_tokens":64,"weakest_assumption_plain":"SGX functionality and execution semantics can be faithfully recreated inside Arm CCA firmware without introducing new attack surfaces or breaking compatibility for real-world applications.","fun_headline_variants_meta":{"raw":{"variants":["CCX Ports Unmodified SGX Apps to Arm CCA","Arm CCA Hosts SGX Apps via CCX Firmware","CCX Recreates SGX Abstractions for Arm CCA","SGX Compatibility on Arm CCA Using CCX"]},"model":"grok-4.3","cost_usd":0.006564,"raw_usage":{"total_tokens":2977,"prompt_tokens":649,"num_sources_used":0,"completion_tokens":62,"cost_in_usd_ticks":65640500,"prompt_tokens_details":{"text_tokens":649,"audio_tokens":0,"image_tokens":0,"cached_tokens":64},"completion_tokens_details":{"audio_tokens":0,"reasoning_tokens":2266,"accepted_prediction_tokens":0,"rejected_prediction_tokens":0}},"tokens_in":649,"tokens_out":62,"duration_ms":27331,"temperature":1.0,"reasoning_tokens":2266,"cache_read_input_tokens":64,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-05-11T02:21:32.045682+00:00","model_set":{"reader":"grok-4.3"},"falsifier":"An existing SGX application that either fails to execute on the CCX prototype, requires source code changes, or shows a security issue not present under native Intel SGX.","supporting_citations":[],"review_version":1}