open_access_plos-svg

Authoring an Article on the Centre for Security Failures Studies’s Blog.

Thank you for choosing to submit your article to us. These instructions will ensure we have everything required so your article can move through peer review and publication smoothly. Please take the time to read and follow them as closely as possible, as doing so will ensure your article matches the blog’s requirements.

Please make sure you have formatted your article according to the blog’s guidelines, as described below. The Centre for Security Failures Studies publishes original, previously unpublished articles and very rarely republishes important articles with authorisations. Drafts of articles should be submitted to any of the blog editors, Stephen Langley and Matthieu Petrigh.

However, before submitting their drafts, authors are encouraged to discuss the theme of their articles with any of the blog editors.

A typical article length is between 1000 and 10000 words with each figure or table counted as 300 words. Please make sure that the text is 1.5-spaced and in 12-point Helvetica. Short biographies for all authors should be provided at the time of submission, along with contact information and an indication of the corresponding author. Submissions will not be considered until a biography is submitted.

Please note that the Centre for Security Failures Studies uses  CopyScape software and Google Search Engine to screen articles for unoriginal material. By submitting your article for publication into the blog of the Centre for Security Failures Studies, you are agreeing to any necessary originality checks your article may have to undergo during the peer review and production processes.

Submission of Drafts

Format and Presentation. The Centre for Security Failures Studies’s Blog requires a main document and its related files such as figures, diagrams, models and pictures. The format of the whole document is 21 x 29.7 cm (8.5″ x 11″ – A4), page orientation is vertical. The main document, which is used for review, must be a Word, Pages or PDF file. Keep acronyms and abbreviations to a minimum and define those that do appear in the text. The appropriate usage of M-dashes and N-dashes would be appreciated. Footnotes are not typically used; if you need to include them, use the endnote format. No company logo, no advertisement, no distraction – only relevant contents (text, tables, diagrams, models and graphics).

Structure. The structure of the article is flexible but must be clear and should include the following: an abstract when the article is over 2000 words, an introduction, few sections, a conclusion and a reference list or list of hyperlinks if appropriate.

Writing Style. Academic or Non-Academic.

Figures, Tables, and Graphics. Upon initial draft submission, figures, tables, and other graphics should be included as part of the main document (embedded). All tables and figures must be mentioned in the text of the article, and include a caption. All illustrations must be clear enough to be read properly when published online. Upon the acceptance of a draft, authors will be asked to submit separate art files (not embedded in text files). Digital files are recommended for highest quality of display and should follow these guidelines:

Weight of 2Mb max
JPEG or PNG format only

Screen shots: Save original screen shot captures in .jpg or .png format at a good resolution.

References. If references have been used, they should appear at the end of the article in APA or Harvard style, except when shown otherwise in the examples listed here. Cite in text the author and date, separated by a comma, in parentheses if using APA, for example (Smith, 2005) or the author and date separated by a colon (Smith: 2005) if using Harvard. For multiple authors, use an ampersand if APA and “and” for Harvard.

Examples:

Journal Article: Clarke R. V. (2004). ‘Technology, criminology and crime science’. European Journal on Criminal Policy and Research, 10: 55-63.

Book: Button M. (2008). Doing security: critical reflections and an agenda for change. Basingstone: Palgrave Macmillan.

Book Chapter: Wakefield A. (2014). ‘Where next for the professionalisation of security?’ in M. Gill (ed.) The handbook of security, Second edition, (pp. 919-35). Basingstone: Palgrave Macmillan.

Conference Proceedings: Schultz A. & Hahsler M. (2002). Software reuse with analysis patterns. In Proceedings of the 8th AMCIS, pp. 1156-1165, Dallas, TX, August 2002. Association for Information Systems.


Electronic Sources: PKF (2015). The financial cost of fraud 2015: what the latest data from around the world shows. Retrieved 24 October 2015, from http://www.pkf.com/media/31640/PKF-The-financial-cost-of-fraud-2015.pdf

Further guidance on APA referencing  can be found here.

Further guidance on Harvard referencing can be found here.

Hyperlinks. If hyperlinks have been used, they must be included in the reference list (endnote) and/or directly embedded into the text if referring to a particular word, rather than an idea (like in Wikipedia).

Examples:

Security is the degree of resistance to, or protection from, harm. It applies to any vulnerable and/or valuable asset, such as a person, dwelling, community, item, nation, or organization. Championed globally by professional associations such as ASIS or the Security Institute, it has been noted by the Institute for Security and Open Methodologies (ISECOM) in the OSSTMM 3, that security provides “a form of protection where a separation is created between the assets and the threat.” These separations are generically called “controls,” and sometimes include changes to the asset or the threat.[1]

[1] “ISECOM – Open Source Security Testing Methodology Manual (OSSTMM). Retrieved 02 December 2016. (To be in the endnote section of the article).

Article Review Process. Once submitted, an article undergoes an initial review by the blog editors. After a positive initial review, the article undergoes a blind review process by two or more subject matter experts. Reviews are then received by the blog editor-in-chief, who then provides the author with an editor’s report that includes the final recommendation: a conditional acceptance, a request for further revisions, or rejection.

Prior to publication, all accepted articles are edited for style and grammar by the Centre for Security Failures Studies’s editor-in-chief. The author is also requested to complete a contractual agreement. If you plan to use graphics, pictures or tables from another publication or online article, you should secure republishing permission from the appropriate original publisher. Such permission is also needed for quotes of 50 words or more, or more than 400 words of material quoted from one source. All accepted articles, artworks, and photographs remain the properties of the Author but are subject to terms and conditions.

Proofs. Articles proofs are sent to the corresponding author before publication. They must be carefully checked and returned within 3 days of receipt. Once published, a hyperlink leading to the published article (permanent link) will be sent by email to the author of the article. Published articles must be carefully checked by clicking on the hyperlink within 24h of receipt.

Open Access. Articles published by the Centre for Security Failures Studies are Open Access and therefore permanently available for free online access immediately after their publication, to anyone, anywhere, at any time. Open Access will work alongside a Creative Common license to be selected by the Author of the article.

More information about Open Access can be found, for example, on Wikipedia at: https://en.wikipedia.org/wiki/Open_access

More information about Creative Commons and their licenses can be found, for example,  at: https://creativecommons.org/licenses/

After Publication

Authors publishing articles with us will have, if they want, their profile displayed on our website. This profile can include a picture, a brief description, a video and a contact form linking to their own email address. Examples of profiles can be found here.

Questions

We are here to clarify doubts, if any. Please use our contact page to raise your concerns.