Muhammad Ikhwanul Hakim
Unknown Affiliation

Published : 2 Documents Claim Missing Document
Claim Missing Document
Check
Articles

Found 2 Documents
Search

PENINGKATAN KADAR NIKEL BIJIH LIMONIT MELALUIPROSES REDUKSI SELEKTIF DENGAN VARIASI WAKTU DAN PERSEN REDUKTOR Muhammad Ikhwanul Hakim
Jurnal Furnace Vol 3, No 1 (2017)
Publisher : Jurusan Teknik Metalurgi

Show Abstract | Download Original | Original Source | Check in Google Scholar | Full PDF (81.991 KB)

Abstract

Abstrak. Indonesia memiliki cadangan bijih laterit dalam jumlah yang melimpah, salah satunya dalam bentuk bijih limonit. Akan tetapi bijih limonit jarang dipilih oleh industri untukdijadikan sebagai bahan baku karena hanya mengandung sedikit nikel. Beberapa proses dapat digunakan untuk meningkatkankadar nikel di dalam bijih limonit, salah satunya adalah prosesreduksi.Proses reduksi merupakanproses untuk mereduksi logam oksida menjadi logam denganmenggunakan reduktor tertentu. Reduksi selektif juga berarti mereduksi logam oksida apa saja danmencegah reduksi senyawa oksida lain yang terdapat pada bijih. Proses ini diharapkan dapatmembebaskan nikel dari pengotornya sehingga akan meningkatkan kadar nikel.Salah satu daerah yang mempunyai cadanganbijih limonit dalam jumlahbesar berada di Sangaji, Halmahera Timurdengan kadar nikel 0,8-1,5% dan besi 40-50% [2] Penelitian dilakukan dengan variabel waktu 30,60, 120 dan 180 menit dengan variasi penambahan reduktor yaitu 0, 7, 14 dan 21%. Analisis awalmenggunakan XRF, XRD dan SEM-EDX. Setelah proses reduksi, sampel dianalisis akhirmenggunakan XRD, SEM-EDX dan AAS untuk mengetahui peningkatan kadar Ni pada sampeltersebut. Kadar Ni optimum yang diperoleh dari variasi waktu yaitu pada waktu 180 menit sebesar1,34% dengan persen ekstraksi sebesar 57,67%. Sedangkan kadar Ni optimum yang diperoleh darivariasi penambahan reduktor yaitu pada penambahan 14% reduktor sebesar 1,74% dengan persenperolehan sebesar 89,35%.
Performance Analysis of the Fuzzing Method in Detecting API Vulnerabilities in Mobile Healthcare Application X Based on OWASP API Security Top 10 Muhammad Ikhwanul Hakim; Radityo Adi Nugroho; Dodon Turianto Nugrahadi; Rudy Herteno; Setyo Wahyu Saputro
Telematika Vol 19, No 1: February (2026)
Publisher : Universitas Amikom Purwokerto

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.35671/telematika.v19i1.3149

Abstract

Traditional perimeter security measures, such as Web Application Firewalls (WAFs) and static analysis, often fail to detect logic-based vulnerabilities in healthcare Application Programming Interfaces (APIs), creating significant risks for patient data confidentiality. Addressing the scarcity of empirical performance evaluations in this domain, this study employs a grey-box controlled experimental design to assess the effectiveness of automated HTTP fuzzing against a production-grade mobile health application ("Application X"). Using the FFUF tool configured with sequential identifier injection, status-code filtering, and hidden-field probing, the experiment tested 33 endpoints against the OWASP API Security Top 10 2023 benchmarks. To ensure data reliability, a rigorous multi-step validation protocol including replay testing and environmental noise elimination was applied to filter false positives. The results identified 88 distinct vulnerabilities distributed across six categories, with a critical dominance of Security Misconfiguration (API8) and Broken Object Property Level Authorization (API3). Analytically, the high prevalence of API3 reveals a systemic failure in backend serialization, where sensitive fieldsĀ  including password hashes and internal administrative flags were exposed due to the absence of Data Transfer Objects (DTOs), contradicting the assumption of secure client-side filtering. Limitations of this study include the restriction to a single patient-role perspective and the exclusion of third-party integrations. The study concludes that automated fuzzing is superior to static analysis in detecting runtime data leakage and recommends mandatory Server-Side Output Filtering through explicit DTOs as a critical standard for secure health API development and data privacy compliance.