One Article Review
| Source |  AlienVault Blog |
|---|---|
| Identifiant | 510530 |
| Date de publication | 2018-03-13 13:00:00 (vue: 2018-03-13 13:00:00) |
| Titre | Infosec Language Grows Up: The Bishop Fox Cybersecurity Style Guide |
| Texte |
On February 15, Bishop Fox released their Cybersecurity Style Guide. I am absolutely stoked for them, and for the arrival of what looks like a new era in InfoSec language consistency.
I was lucky enough to get to speak to Technical Editor Brianne Hughes last week. “I polled the internal team,” she told me, “and got the https://willusingtheprefixcybermakemelooklikeanidiot.com/ sent back to me a few times. We need to be consistent as a department – Engineers want to know why, they want transparency, and they don’t want to be told what to do. We have lively dialog in the comments of our reports.”
She went on to say, “InfoSec merges hacker slang and military jargon in a corporate setting, and it’s hard to find middle ground. The language itself is a kind of slang, and the point of slang is to identify in-groups and out-groups, so there’s a definitely border built up that were looking to poke holes in to facilitate future conversations.”
Largely, those of us lucky enough to work for InfoSec companies enlightened enough to know that having editorial services available is a good thing, have mostly done our thing solo, and we’ve collected language that’s specific for our company. As a new editor in that position, there’s always that little moment of hesitation, where you try to decide what style guide to leverage. Microsoft, with its monolithic 1990’s tablet-down-from-the-mount style guide? Sun Microsystems, where once upon a time the collective Editorial staff met to decide the proper way to write “readme,” only to decide after four straight hours of heated argument that since the users knew what we meant, we would willfully refuse to standardize?
There’s the Yahoo Style Guide, the Salesforce Style Guide… everyone’s got one, and most editors have a favorite. But this is the first time I’m aware of that someone specifically in the world of InfoSec has taken a stab at creating something like unification, by not only creating a guide, but actively promoting it, and soliciting input from across the industry. “I made this for myself because I needed it,” says Brianne. “And I was lucky enough to have the skills and the support. It’s a beautiful environment where Bishop Fox has been around 12 years, but allows for passion projects.”
The second it downloaded, I sat down and read every word. You guys… this is superlative. Some highlights include:
A technical formatting section simple enough to cover our needs, without going over the top to cover every possible contingency.
An appendix explaining how decisions were made. This is particularly glorious, because mostly, we’re winging it. The Wild West style of InfoSec netymology has meant that most of us within our silos make a choice, and call it done. There’s been very little in the way of guidance about how to make those decisions. I think that if we, as editorial professionals, can help each other make consistent choices, the entire field will mature more rapidly, and that is all to the good for improving consistency and transparency of dialog between professionals and their clients.
Another appendix for external resources. This is so beautifully thought-out, so comprehensive… I felt myself sighing in pure appreciation. I personally ha |
| Envoyé | Oui |
| Condensat | “and “i “i’d “infosec “readme 1990’s about absolutely accepting across actively after alienvault all allows alternatives always another anyone appendix appreciation are aren’t argument around arrival assurance available aware back baseline beautiful beautifully because been before being best between bishop border brianne built but buy call can chair cheering choice choices cited clear clients collected collective com com/ comments community companies company comprehensive… conscious consistency consistent contingency conversations coolest corporate cover creating cybersecurity decide decisions definitely department dialog different does don’t done down downloaded each editor editorial editors engineers enlightened enough entire entry environment era especially every everyone everyone’s evidenced exactly excluding explaining external facilitate favorite february felt field find first formatting four fox frivolously from fun future get glorious going good got ground groups grows guidance guide guide… guys… hacker hard has have having heated help here here: hesitation highlights holes hours how https://willusingtheprefixcybermakemelooklikeanidiot hughes humor i’d i’m identify improving include: industry infosec input internal it’s its itself jargon kind knew know language largely last leverage like list little lively looking looks love lucky made majority make mature meant meet merges merriam met microsoft microsystems middle military moment monolithic more most mostly mount myself need needed needs netymology new not now… once one only other out over participation particularly passion passively person personally picked platform pleased point poke polled position possible preferences professionals projects promoting proper providing puns pure qa: quality rapidly rather read real refuse released reports resources salesforce sat say says second section security see sent services setting share she short sighing silos simple since skills slang soliciting solo some someone something somewhat speak specific specifically stab staff standardize standing start stoked straight style style@bishopfox suggestions sun superlative support tablet taken team technical than that’s them there’s thing think thinking those thought time times told top transparency try tweet unification up: upon use users verve… very voice want way we’re we’ve webster webster’s week welcome welcomed welcoming well went west what where who whole why wild will willfully winging within without word work world would write write…part yahoo years |
| Tags | |
| Stories | Yahoo |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.