Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN SecurityDNN Security
Previous
 
Next
New Post
6/8/2006 5:08 PM
 

As a new user of DNN, I am somewhat concerned about blog entries pointing to security issues primarily associated with third party applications.  Since many DNN applications utilize some number of third party modules, how does one build a web site and represent that it is secure - or at least, as secure as it would be if the web site were build in any other fashion?.  Furthermore, if a vulnerabiity is identified, what certainty can there be that a third party will react quickly to repair the module?  Does anyone have any definitive data that indicates if this is a real problem or not?  Should a potential recipient of a DNN/Third party created web site be concerned about security issues any more so than other users? 

As someone who is considering using DNN to build web sites for my clients, should I expect my clients to object to the choice of DNN because of these perceived security issues?  How do you address these issues with your clients?

 

Albert

 
New Post
6/8/2006 6:09 PM
 

Actually theres only 1 blog post - and it's the first reported issue in a 3rd party module I know of.

We plan to offer a module certification service at some point, and security audits will comprise a part of that, which I'm sure will be a popular addition. Apart from that all I can do is recommend that you purchase modules from reputable sources, and if you are concerned about potential security issues, you purchase the source, so you can either audit it yourself/pay for someone to do it, and are not dependant on the module provider if you need to make a fix at some point.

Realistically IMHO anything beyond a simple system will include components from 3rd parties such as modules,skins, controls etc., this is not a Dotnetnuke issue, but one that affects all products of reasonable power and complexity.

Cathal

With regards 3rd party applications,


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN SecurityDNN Security


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out