PVPs

  • Comments posted to this topic are about the item PVPs

  • What is a private virtual property (PVP)? I have not heard this term before.

  • Buy a certificate from GoDaddy and they won't let you forget. You will get many, many reminders. (I wish they had a way to turn them off when you actually didn't intend to renew a certain certificate or domain!)

  • From an operational perspective, I think I would treat the PVP as an external service being subscribed to by the company, and managed as such within the company's ITSM system. This should allow better visibility and awareness of upcoming expirations/renewals. In addition, the procedures for creating/renewing/installing certs should be documented up front within the ITSM system.

    As Forbes points out in their "three reasons why PVPs get overlooked", "in every case the problem is a failure to plan strategically". The three issues they describe are symptomatic of a lack of a capable ITSM system and/or lack of capable management to utilize that system properly.

  • jvanbeek (12/12/2013)


    Buy a certificate from GoDaddy and they won't let you forget. You will get many, many reminders. (I wish they had a way to turn them off when you actually didn't intend to renew a certain certificate or domain!)

    Except those notes come to you. What if you've left the company?

  • TGwinn (12/12/2013)


    From an operational perspective, I think I would treat the PVP as an external service being subscribed to by the company, and managed as such within the company's ITSM system. This should allow better visibility and awareness of upcoming expirations/renewals. In addition, the procedures for creating/renewing/installing certs should be documented up front within the ITSM system.

    As Forbes points out in their "three reasons why PVPs get overlooked", "in every case the problem is a failure to plan strategically". The three issues they describe are symptomatic of a lack of a capable ITSM system and/or lack of capable management to utilize that system properly.

    I agree, if you have some ITSM system in place. Sometimes it's ad hoc and the people handling various pieces don't know about things like domain names, certificates, etc.

  • The author bought it, the accountant should have gotten a note to put in on the purchase calendar.

    Throw in some turnover or email conversions and it gets more fun.

  • Business frequently talks about continuity plans and disaster recovery. And the two go hand-in-hand. But it's frequently TALK.

    Continuity plans talk about business continuity (and that's frequently implemented) but not JOB continuity. What happens when a single person moves on? What do they do? What are their processes and contacts? Those are almost as critical in a business. The military covers it with Continuity folders - especially for one or two-deep positions (or you are SUPPOSED to have one). But it's seems to be lacking in the business world. Internal blogs and wikis server some of the same process, but it's almost as if their is information hoarding as opposed to information sharing.

    Timothy J. Bruce

  • Steve Jones - SSC Editor (12/12/2013)


    Except those notes come to you. What if you've left the company?

    I have made a habit at my last and current company that whenever I am getting something that that is a timed purchase or even setting an e-mail account to send or receive SQL email the recipient is a group account as well as the send account has multiple auto-forward recipients.

    So if I leave the company and my mail/AD account has been disabled there are others getting the e-mails. If they don't act on it or realize the issue, it is not my fault.



    ----------------
    Jim P.

    A little bit of this and a little byte of that can cause bloatware.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply