4/12/2022
35

Poker is any of a number of card games in which players wager over which hand is best according to that specific game's rules in ways similar to these rankings.Often using a standard deck, poker games vary in deck configuration, the number of cards in play, the number dealt face up or face down, and the number shared by all players, but all have rules that involve one or more rounds of betting. Blur secures ALL the personal information you put online - making it safe, fast, and easy to login and checkout from your browser, phone, or tablet. Here at Betfair Poker you'll find an introduction to the fundamental poker strategy concepts you need to know in order to make a success of yourself at the felt. Sitting down in any game of poker, online or live, can be daunting, but once you've mastered the basics then the road to success is a lot less treacherous. A reduction in the number of people remaining in a hand. EXAMPLE: 'I had a decent hand but was afraid of being outdrawn, so I raised for protection.' APPLIES TO: Online and Land-based Venues. RELATED TERMS: Outdraw, Protect, Protection Bet.

Poker Card Protectors Funny

Become the next The Platinum!
Our Monthly Quest awaits you
Rush & Cash Daily $40,000 Leaderboard
You can't miss it!
Did you have a hard day on the felt?
Don't worry, there's GG Care!
PreviousNext

Why Betkings

Not just another gaming website: with BetKings you are joining the idea that game is not always about numbers, right calls and strategy. Above everything there is one thing gaming should be: FUN.

Jackpot

Poker

AOF Jackpot

Short Deck Flush Jackpot

Big Hand Jackpot

Play Anywhere

With refined desktop and mobile experiences, you can always find a table whenever you like. Have just a couple of minutes? All in or Fold on your phone it is then!

Available on

Our App Features

Find out why our software is just so good for your poker fun!

Protection Poker Tutorial
Laurie Williams

Database tables

Tables to complete

Tutorial slides [Contact Laurie Williams at williams ~ at ~ csc dot ncsu dot edu for the Power Point slides]

In this exercise, we willbe using a variant of Planning Poker – called Protection Poker – to do asecurity risk assessment of the new capabilities provided by the teamproject.Ultimately, we come out with aranking of the security risk of each of the new requirements for theiteration.Requirements with highersecurity risk should get more attention when it comes of “building security in”to your product and to verifying that security protection mechanisms are inplace and working.Protection Poker is done during an iteration planning meeting.

We use the following computation for security risk:security risk = (ease of attack)(value ofasset being protected)

Poker

The following chart can help to clarify this thinking:

Both Planning Poker and Protection Poker work when members feel free toexpress their opinion, diversity of opinion is encouraged, and everyone is opento learning from the others.

Background

The tutorial is based on a hypothetical system called iTrust[1].iTrust is a role-based heath careweb application.Through the system, patients cansee an manage their own medical records.Medical personnel can manage the medical records of their patientsincluding those provided by other medical personnel, be alerted of patientswith warning signs of chronic illness or missing immunizations, and performbiosurveillance such as epidemic detection.

Prerequisite

Knowledge of the Planning Poker practice for effort estimation.

Tutorial steps

1.Calibratevalue of database tables.Look atthe database tables (provided in Table 1).

a.As a team, think about which table could beconsidered “the” least valuable table to an attacker.Circle the name of the database and givethat table a value of 1 in Table 1.

b.As a team, think about which table could beconsidered the “most” valuable table to an attacker.Use your “poker” cards to come to consensusabout how much more valuable that table is to an attacker than the previoustable.Circle the name of the databaseand record the value in Table1.

These are your two endpoints forthe rest of the Protection Poker exercise, though you can certainly updatethese values if you change your opinion or learn new information.

2.Calibrateease of attack for new requirements.Lookat the new requirements and tryto cometo a consensus on the requirement that will make an attack easiest and therequirement that will make the attack hardest for an attacker to exploit thenew functionality.Here is a partiallist of things to consider.Use your “poker” cards to assign ease pointsto the hardest and easiest to attack.Record these ease points in Table 3 for theappropriate requirement.These are yourtwo endpoints for the rest of the Protection Poker exercise, though you cancertainly update these values if you change your opinion or learn newinformation.

3.Computesecurity risk.For each requirement,perform the following steps:

a.Identify each database table used by the newcapabilities provided by that requirement.Document the names of these tables in Table 2.If a new table will need to be created forthis requirement, name it and write this name in Table 2.

b.For each table identified in step 2a, look in Table 1 to see if thetable has been assigned a value.

·If yes, copy the value into Table 2.

·If no, use your poker cards to assign thatdatabase table a value, considering the relative values assigned in Step1.Record that value in Table 1 and Table 2.

c.Put the sum of the values of all the database tables in Table 2 in the “value” points for therequirement in Table 3.

Poker Protection Book

d.Consider ease points for the remaining fiverequirements – how easy does the new capability make an attack for someone withmalicious intent?Use your “poker”cards to assign a value for ease points for each requirement.Record the value in Table 3.

e.Compute security risk by multiplying the valuepoints (step 3c) by ease points (step 3d).Record the value for security risk in Table 3.

Open Source Risk Game

4.Ranksecurity risk.Once you havecomputed the value for security risk for each requirement, provide a rankingnumber for each requirement in the last column of Table 3 where therequirement with the highest security risk is given a 1 and the lowest securityrisk a 4.As you develop your project,use these rankings to consider how much security attention to pay to each ofthese requirements.Looking at yourrisk rankings, is any rank surprising to you? Discuss as a group any surprisesin your prioritization, and how well you are satisfied with both the values andthe ranks.