in reply to SWOT-analysis

Also under risks it's probably worth looking at security risks. How secure is your app? Do you use taint mode? Will installing your app compromise a site's security?

--
<http://www.dave.org.uk>

"The first rule of Perl club is you don't talk about Perl club."

Replies are listed 'Best First'.
Re: Re: SWOT-analysis
by arhuman (Vicar) on Oct 31, 2001 at 18:42 UTC
    As often davorg is right, common spots to examine when talking about security are :
    • Possible denial of service
    • Access control
      How to restrict/setup rights to access/modify/delete data or resources.
    • Authentication
      Especially way to bypass it or impersonate someone.
    • Data integrity
      Protect your data againts corruption deletion...
      I'm not only talking about physical integrity but also about logical one (to prevent injection of fake data or the creation of an incoherent state in your data)


    "Only Bad Coders Code Badly In Perl" (OBC2BIP)
[reply]

In Section Meditations