Peer Review History
| Original SubmissionNovember 12, 2024 |
|---|
|
Dear Dr. Alnasrallah, Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process. Please submit your revised manuscript by Mar 05 2025 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org . When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.
If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter. If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols . Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols . We look forward to receiving your revised manuscript. Kind regards, mamoona humayun Academic Editor PLOS ONE Journal Requirements: 1. When submitting your revision, we need you to address these additional requirements. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and 2. Please note that PLOS ONE has specific guidelines on code sharing for submissions in which author-generated code underpins the findings in the manuscript. In these cases, we expect all author-generated code to be made available without restrictions upon publication of the work. Please review our guidelines at https://journals.plos.org/plosone/s/materials-and-software-sharing#loc-sharing-code and ensure that your code is shared in a way that follows best practice and facilitates reproducibility and reuse. 3. We note that your Data Availability Statement is currently as follows: [All relevant data are within the manuscript and its Supporting Information files.] Please confirm at this time whether or not your submission contains all raw data required to replicate the results of your study. Authors must share the “minimal data set” for their submission. PLOS defines the minimal data set to consist of the data required to replicate all study findings reported in the article, as well as related metadata and methods (https://journals.plos.org/plosone/s/data-availability#loc-minimal-data-set-definition ). For example, authors should submit the following data: - The values behind the means, standard deviations and other measures reported; - The values used to build graphs; - The points extracted from images for analysis. Authors do not need to submit their entire data set if only a portion of the data was used in the reported study. If your submission does not contain these data, please either upload them as Supporting Information files or deposit them to a stable, public repository and provide us with the relevant URLs, DOIs, or accession numbers. For a list of recommended repositories, please see https://journals.plos.org/plosone/s/recommended-repositories . If there are ethical or legal restrictions on sharing a de-identified data set, please explain them in detail (e.g., data contain potentially sensitive information, data are owned by a third-party organization, etc.) and who has imposed them (e.g., an ethics committee). Please also provide contact information for a data access committee, ethics committee, or other institutional body to which data requests may be sent. If data are owned by a third party, please indicate how others may request data access. Additional Editor Comments: Dear Authors, Thank you for submitting your manuscript titled “Enhancing IDS for the IoMT based on Advanced Features Selection and Deep Learning Methods to Increase the Model Trustworthiness” to PLOS ONE. After careful evaluation of the reviewers’ comments, I have decided that the manuscript requires Major Revision before further consideration. While one reviewer suggested minor revisions, the other recommended rejection. Considering the potential value of the work and the feedback provided, I believe the manuscript could be suitable for publication after addressing the reviewers’ concerns comprehensively. Please revise your manuscript in accordance with the reviewers' comments and submit the updated version within 30 days. [Note: HTML markup is below. Please do not edit.] Reviewers' comments: Reviewer's Responses to Questions Comments to the Author 1. Is the manuscript technically sound, and do the data support the conclusions? Reviewer #1: Partly Reviewer #2: Yes ********** 2. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #1: No Reviewer #2: Yes ********** 3. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #1: Yes Reviewer #2: Yes ********** 4. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #1: No Reviewer #2: Yes ********** Reviewer #1: The authors propose an IDS model for the IoMT that improves security and efficiency in the categorization of the detection process through the use of advanced feature selection approaches. Organization of the article is poor. The figures are not embedded in the text which affects the readability of the text. Even though the title says IoMT, all data sets and not IoMT datasets Many abbreviations are used which are not expanded during their first use. Methodology is not clear. Since the paper uses advanced feature selection process, comparison has to be done with reference to the features selected and the importance of these feature in the real life context. Result Analysis is also not satisfactory. Lot of grammatical errors are there. Thorough proofreading has to be done. Reviewer #2: The abstract is well-written, and the topic is interesting. Provide a brief mention of numerical improvements (e.g., percentage increase in accuracy or F1 score). Why were IG and RFE chosen over other feature selection methods? A brief rationale could strengthen the argument. The use of Deep Autoencoder for dimensionality reduction is valid, but its specific advantage in this context needs clearer articulation. Clarify how the proposed combination of IG, RFE, and Deep Autoencoder differs from or improves upon prior works. Highlight why selecting the top 50% of features is optimal. While the datasets are mentioned, their relevance to IoMT and the specific challenges they address are not fully explained. Why are these datasets suitable for evaluating IoMT IDS? IDS and IoMT are defined again and again while they should be abbreviated at 1 time only when it is first used. The description of methods like IG, RFE, and DAE lacks a deeper explanation of why these specific techniques were chosen over others. While their functionality is described, the rationale for their selection in the IoMT context is missing. The section on Deep Neural Networks (DNNs) is generic and lacks details specific to the study, such as the architecture, hyperparameters, or training strategies used. Discuss the scalability of these methods and their potential deployment in practical IoMT applications. Mention challenges such as data privacy, device compatibility, or computational constraints in real-time scenarios. Highlight why the TFS-U subset outperformed other subsets in the CICIDS2017 and WUSTL-EHMS-2020 datasets. Emphasize the novelty and advantages of combining DAE and DNN with selected features. Discuss any challenges or limitations encountered in your study, such as computational costs, reliance on specific datasets, or potential overfitting. Reflect on why certain feature subsets like TFSIG or TFSRFE underperformed relative to TFS-U. While the model is stated to be suitable for real-time threat detection, there is no mention of potential latency or resource constraints. Although the model is said to reduce computational complexity, no quantitative evidence is provided in the conclusion. Specific directions for improvement, such as integrating more diverse datasets, optimizing the model for resource-constrained environments, or addressing new threat types, are missing ********** what does this mean? ). If published, this will include your full peer review and any attached files. If you choose “no”, your identity will remain anonymous but your review may still be made public. Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy Reviewer #1: No Reviewer #2: No ********** [NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.] While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/ . PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org . Please note that Supporting Information files do not need this step. |
| Revision 1 |
|
Dear Dr. Alnasrallah, Thank you for submitting your manuscript to PLOS ONE. After carefully considering the reviewers’ assessments, we are requesting a major revision of your manuscript to address the concerns outlined below.
Please submit your revised manuscript by May 16 2025 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org . When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file. Please include the following items when submitting your revised manuscript:
If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter. If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols . Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols . We look forward to receiving your revised manuscript. Kind regards, mamoona humayun Academic Editor PLOS ONE Comments to the Author Reviewer #2: All comments have been addressed Reviewer #3: (No Response) ********** 2. Is the manuscript technically sound, and do the data support the conclusions?-->?> Reviewer #2: (No Response) Reviewer #3: Partly ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #2: (No Response) Reviewer #3: No ********** 4. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #2: (No Response) Reviewer #3: Yes ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #2: (No Response) Reviewer #3: Yes ********** Reviewer #2: (No Response) Reviewer #3: 1. The authors state that they have reorganized the article. Issue: There is no explicit mention of how the structure was improved. The response is vague and lacks specific details on how readability, logical flow, or coherence has been enhanced. 2. The authors justify CICIDS2017 by stating that it contains attacks relevant to IoMT environments. Issue: CICIDS2017 is still a general IoT dataset, not an IoMT-specific one. Their justification does not fully address why a non-IoMT dataset is suitable. 3. They reviewed and expanded abbreviations at first mention. Issue: This needs verification. If certain abbreviations remain undefined upon first usage, they need to correct this systematically. 4. They added details on IG and RFE selection, as well as the impact of feature selection. Issue: The response focuses on theoretical justification but does not compare the selected features with alternative feature selection methods or explain the practical significance of these features in a real IoMT deployment. An explicit comparison with alternative selection methods and a deeper justification of why the chosen features matter in an IoMT-specific security context is needed to be included. 5. They expanded on the discussion, added confusion matrices, and included additional tables. Issue: There is still insufficient discussion on practical implications, statistical significance of improvements, and how these findings translate into real-world benefits for IoMT networks. The authors should provide deeper insights into what these results mean in practical IoMT deployments—how do they handle adversarial attacks, real-time performance in constrained environments, and device heterogeneity? 6. They mentioned improvements in execution time and memory efficiency. Issue: The response lacks a detailed latency analysis for real-time scenarios and does not quantify computational overhead. The authors should at least include numerical latency measurements, resource utilization data, and a discussion of the challenges in deploying the model on low-power IoMT devices. 7. They provided reduced training time and memory consumption statistics. Issue: The provided numbers do not compare their approach with alternative methods or justify trade-offs. Reducing complexity while retaining model effectiveness in real-time applications is critical. Comparisons with other lightweight IDS models and a justification for why this specific trade-off is optimal are needed. 8. They added general directions for future research. Issue: The proposed future work remains superficial. It lacks a concrete roadmap addressing: How their model can be optimized for new IoMT attack types. How they plan to validate performance in real IoMT environments. Potential integration with real-world medical devices and compliance with IoMT security standards (e.g., HIPAA, GDPR). ********** what does this mean? ). If published, this will include your full peer review and any attached files. If you choose “no”, your identity will remain anonymous but your review may still be made public. Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy Reviewer #2: No Reviewer #3: No ********** [NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.] While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/ . PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org . Please note that Supporting Information files do not need this step. |
| Revision 2 |
|
Dear Dr. Alnasrallah, Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process. Please submit your revised manuscript by Jun 28 2025 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org . When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.
If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols . Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols . We look forward to receiving your revised manuscript. Kind regards, mamoona humayun Academic Editor PLOS ONE Journal Requirements: Please review your reference list to ensure that it is complete and correct. If you have cited papers that have been retracted, please include the rationale for doing so in the manuscript text, or remove these references and replace them with relevant current references. Any changes to the reference list should be mentioned in the rebuttal letter that accompanies your revised manuscript. If you need to cite a retracted article, indicate the article’s retracted status in the References list and also include a citation and full reference for the retraction notice. Reviewers' comments: Reviewer's Responses to Questions Comments to the Author Reviewer #2: All comments have been addressed Reviewer #3: (No Response) ********** 2. Is the manuscript technically sound, and do the data support the conclusions??> Reviewer #2: Yes Reviewer #3: Partly ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #2: Yes Reviewer #3: Yes ********** 4. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #2: Yes Reviewer #3: Yes ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #2: Yes Reviewer #3: No ********** Reviewer #2: (No Response) Reviewer #3: This manuscript proposes an intrusion detection system (IDS) framework for the Internet of Medical Things (IoMT), integrating Information Gain (IG) and Recursive Feature Elimination (RFE) for feature selection, Deep Autoencoder (DAE) for dimensionality reduction, and Deep Neural Network (DNN) for classification. While the authors have made significant improvements in this revision and addressed most reviewer suggestions, several areas still require clarification or further elaboration: 1. The abstract still includes high-level claims (e.g., “enhances detection efficiency”) but does not clearly describe the pipeline components (IG, RFE, DAE, DNN) or mention statistical significance tests. Suggestion: Revise the abstract to explicitly outline the full model pipeline and include key statistical validation elements such as “99.82% ± 0.16 accuracy on WUSTL-EHMS-2020 with p < 0.001.” 2. The response outlines prior works and justifies IG + RFE, but the architectural innovation and integration rationale remain vague. Suggestion: Include an ablation study comparing: (1) IG-only, (2) RFE-only, (3) IG+RFE, and (4) IG+RFE+DAE to demonstrate the performance gain from each module. Clarify why this combination is particularly beneficial in IoMT. 3. The manuscript does not incorporate or mention any interpretability tool (e.g., SHAP, LIME) or provide qualitative analysis. Suggestion: Add a discussion on interpretability limitations and propose Grad-CAM or SHAP integration as future work for clinical usability. Interpretability is essential for trust in medical systems. 4. Authors acknowledge not performing hardware-specific latency analysis and only include memory and training time. Suggestion: Report approximate inference latency per sample and FLOPs. Mention specific low-power devices (e.g., Raspberry Pi, Jetson Nano) and expected deployment feasibility. If empirical results are not available, cite similar works for estimation. 5. While the manuscript includes several foundational works on IoMT security and feature selection, it omits recent and relevant studies on lightweight intrusion detection, feature optimization strategies, and AI-based real-time threat analysis in IoT/IoMT environments. These omissions limit the depth and currency of the literature review. Suggestion: Incorporate and discuss the following peer-reviewed works to enhance the contextual framework and align the proposed IDS model with the current state-of-the-art in AI-driven cybersecurity: Sana et al. (2024). Securing the IoT cyber environment: Enhancing intrusion anomaly detection with vision transformers. IEEE Access. https://doi.org/10.1109/ACCESS.2024.3404778 → Demonstrates a modern transformer-based IDS architecture with strong performance on IoT data, offering a meaningful comparison point for your deep learning approach. Dai et al. (2024). An intrusion detection model to detect zero-day attacks in unseen data using machine learning. PLoS ONE, 19(9), e0308469. https://doi.org/10.1371/journal.pone.0308469 → Provides insight into generalization and robustness for detecting unknown threats, which is particularly relevant given your use of CICIDS2017. Yee et al. (2024). A Systematic Literature Review on AI-Based Methods and Challenges in Detecting Zero-Day Attacks. IEEE Access, 12, 144150–144163. https://doi.org/10.1109/ACCESS.2024.3455410 → Offers a comprehensive survey of AI approaches to zero-day detection and can support your justification for using hybrid and dimensionality-reducing models like IG+RFE+DAE. He et al. (2024). SeizureLSTM: An optimal attention-based trans-LSTM network. Biomedical Signal Processing and Control, 96, 106603. https://doi.org/10.1016/j.bspc.2024.106603 → Highlights architectural design choices involving attention and feature integration in time-sensitive medical contexts, offering transferable insights to IoMT IDS development. Incorporating these references would enrich the literature review, strengthen the justification for the proposed hybrid model, and demonstrate alignment with cutting-edge research in AI-driven IoMT security. 6. The comparison focuses mostly on prior DNN-based models; non-DNN or transformer-based IDS are not addressed. Suggestion: Expand the Related Work section to discuss transformer-based models (e.g., Vision Transformer IDS), SVM-based lightweight IDS, or federated IDS approaches. This contextualizes your model better within the broader research space. 7. Figures have been included, but clarity and resolution are still suboptimal. ROC curves and ablation tables are hard to read. Suggestion: Re-render all figures at high resolution, ensure axis labels and legends are visible, and include a consolidated summary table comparing all feature subsets (IG, RFE, union, intersection) in one place. 8. There are redundant claims (e.g., high accuracy, low memory) across abstract, results, and conclusion. Suggestion: Refactor the conclusion to emphasize insight over repetition. Avoid qualitative phrases like “perfect accuracy” without statistical evidence. Use “statistically significant improvement” instead. ********** what does this mean? ). If published, this will include your full peer review and any attached files. If you choose “no”, your identity will remain anonymous but your review may still be made public. Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy Reviewer #2: No Reviewer #3: No ********** [NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.] While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/ . PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org |
| Revision 3 |
|
Enhancing IDS for the IoMT based on Advanced Features Selection and Deep Learning Methods to increase the model trustworthiness PONE-D-24-51421R3 Dear authors, We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements. Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication. An invoice will be generated when your article is formally accepted. Please note, if your institution has a publishing partnership with PLOS and your article meets the relevant criteria, all or part of your publication costs will be covered. Please make sure your user information is up-to-date by logging into Editorial Manager at Editorial Manager® and clicking the ‘Update My Information' link at the top of the page. If you have any questions relating to publication charges, please contact our Author Billing department directly at authorbilling@plos.org. If your institution or institutions have a press office, please notify them about your upcoming paper to help maximize its impact. If they’ll be preparing press materials, please inform our press team as soon as possible -- no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org. Kind regards, mamoona humayun Academic Editor PLOS ONE Comments from PLOS Editorial Office : We note that one or more reviewer has recommended that you cite specific previously published works in the current and previous rounds of revision. As always, we recommend that you please review and evaluate the requested works to determine whether they are relevant and should be cited. It is not a requirement to cite these works and you may remove any added citations before the manuscript proceeds to publication. We appreciate your attention to this request. Additional Editor Comments (optional): Reviewers' comments: |
| Formally Accepted |
|
PONE-D-24-51421R3 PLOS ONE Dear Dr. Alnasrallah, I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS ONE. Congratulations! Your manuscript is now being handed over to our production team. At this stage, our production department will prepare your paper for publication. This includes ensuring the following: * All references, tables, and figures are properly cited * All relevant supporting information is included in the manuscript submission, * There are no issues that prevent the paper from being properly typeset You will receive further instructions from the production team, including instructions on how to review your proof when it is ready. Please keep in mind that we are working through a large volume of accepted articles, so please give us a few days to review your paper and let you know the next and final steps. Lastly, if your institution or institutions have a press office, please let them know about your upcoming paper now to help maximize its impact. If they'll be preparing press materials, please inform our press team within the next 48 hours. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org. If we can help with anything else, please email us at customercare@plos.org. Thank you for submitting your work to PLOS ONE and supporting open access. Kind regards, PLOS ONE Editorial Office Staff on behalf of Dr. mamoona humayun Academic Editor PLOS ONE |
Open letter on the publication of peer review reports
PLOS recognizes the benefits of transparency in the peer review process. Therefore, we enable the publication of all of the content of peer review and author responses alongside final, published articles. Reviewers remain anonymous, unless they choose to reveal their names.
We encourage other journals to join us in this initiative. We hope that our action inspires the community, including researchers, research funders, and research institutions, to recognize the benefits of published peer review reports for all parts of the research system.
Learn more at ASAPbio .