(ISC)² Twitter Updates

  • (ISC)² Twitter Updates

    About the
    (ISC)² Blog

    • (ISC)² believes in the importance of open dialogue and collaboration, between both (ISC)², its certified members and members of business and society.

      (ISC)² established this blog to provide a voice to its certified members, who have significant knowledge and valuable insights to share that can benefit the information security industry, the people in it and the public at large.

      The postings on this site are the author's own and don't necessarily represent
      (ISC)²'s positions, strategies or opinions. (ISC)² does not control, monitor, or endorse any links provided in this blog and makes no warranty or statement regarding the content on any linked website.

      Those who post comments to blogs should ensure their comments are focused on the topic at hand. (ISC)² reserves the right to remove any post or comment from this site.

      Should you find objectionable content in this blog, please notify us as soon as possible at blog@isc2.org.

      Please click here for FAQs.

      Please click here for the Blog guidelines.

    Enter your email address:

    Delivered by FeedBurner

    « Should the CISSP CBK be expanded to cover "human factors" in security? | Main | Weekly Summary of the "DHS Daily Open Source Infrastructure Report" »

    10 August 2009

    TrackBack

    TrackBack URL for this entry:
    http://www.typepad.com/services/trackback/6a00e54f109b6788340120a539380e970c

    Listed below are links to weblogs that reference Add "human factors"? No.:

    Comments

    So, what you are saying Rob is that you have the opportunity to address the human factors while teaching the CBK. Those who self-study, may not get the benefit of those inferences in the material they use.

    "If you want to talk about whether we need to pull all the human factors stuff out, and put it in a separate domain, that's a different question."

    I would say that is by far the more interesting question. You make your point that human factors are already addressed, but this speaks to whether they are addressed in a format and degree that lines up with their true importance:

    "We'd have a human factors domain that takes up three days of a five day seminar, and have to squish the existing domains into the remaining two days."

    So...what's the problem? That really ought to be taken as a sign about the true importance of human factors in security. What that says to me (if true) is that perhaps it is technical solutions that should be piggybacked onto various human factors domains, not the other way around. This potential "imbalance" is really only a problem if one is stuck in the mode of thinking that human factors must be a secondary issue.

    I'm in no position to say that the industry needs to be entirely re-architected around human factors. But given that technology has run so far ahead, and that human factors have been by far the weakest link in the security realm for decades now, I think it's worth considering.

    I would propose, too, that as far as the technical side goes, the main problem remaining to us is making it effortless and intuitive for societies of humans to use the technical solutions already available to them.

    Just another $0.02 for the discussion.

    The comments to this entry are closed.

    The (ISC)² bloggers

    • Tipton W. Hord Tipton, CISSP-ISSEP, CAP, (ISC)² Executive Director
      Schmidt Prof. Howard A. Schmidt, CISSP, CISM (Hon.)
      Sarah E. Bohne, Director of Communications & Member Services

    Recent Contributors

    Past Contributors